Skip to main content
Glama

getecoback-climate-weather

stromtarif_teilgarantie_szenario

Read-only

Preisänderung unter einer nur teilweise geltenden Preisgarantie durchspielen. — Stress-test the annual cost when only part of a tariff is covered by a price guarantee.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "jahres_kwh": "<jahres_kwh>",
      "grund_jahr": "<grund_jahr>",
      "garantiert": "<garantiert>",
      "ungeschuetzt": "<ungeschuetzt>",
      "aenderung_prozent": "<aenderung_prozent>"
    },
    "name": "stromtarif_teilgarantie_szenario"
  }
}

Input Schema

NameRequiredDescriptionDefault
garantiertYesGeschützter Anteil des Arbeitspreises in Brutto-€/kWh.
grund_jahrYesAls unverändert angenommener Jahresgrundpreis in Euro.
jahres_kwhYesJahresverbrauch in kWh.
ungeschuetztYesHeutiger ungeschützter Anteil in Brutto-€/kWh.
aenderung_prozentYesAngenommene Änderung nur des ungeschützten Teils in Prozent.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The annotations already establish that this is a safe, closed-world read/compute operation, so the bar is lower. The description adds only that the scenario concerns a partially covered guarantee, and it does not disclose the calculation model, whether results are deterministic, or what the returned figures represent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the German operation statement, no padding. It is efficient, though the statement sentence and the post-dash sentence are close paraphrases in two languages, which is mildly redundant rather than wasteful.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a five-parameter calculation with no output schema, the description should clarify the shape of the result (annual cost, delta, per-component breakdown), and it does not. Annotations cover the safety profile and the schema covers all inputs, so nothing critical is missing, but the agent must infer the return value.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so all five parameters are fully documented with units, ranges, and semantics in the schema itself. The description's phrase 'only part of a tariff is covered' loosely maps to the garantiert versus ungeschuetzt split but adds no format, unit, or interaction detail beyond the schema. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific operation on a specific object: stress-testing ('durchspielen') cost under a price guarantee that only partially applies. It is clearly distinct from flat tariff calculators among the siblings, but it never says what makes the 'partially covered' scoping different from those alternatives by name.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The condition 'when only part of a tariff is covered by a price guarantee' implicitly signals when the tool applies, which is a usable trigger. However, there is no explicit statement of when NOT to use it, no comparison with siblings such as stromtarif_boersenpreis_endpreis or stromtarif_verbrauchsgewichteter_preis, and no prerequisite or assumption stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources