Skip to main content
Glama

getecoback-raumklima

stromtarife_bonus_vergleichen

Read-only

Zwei Stromtarife mit Bonus, Wechselkosten und Folgekosten vergleichen. — Compare two electricity offers including one-time incentives and recurring costs.

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": {
      "jahresverbrauch_kwh": "<jahresverbrauch_kwh>",
      "arbeit_a": "<arbeit_a>",
      "grund_a": "<grund_a>",
      "bonus_a": "<bonus_a>",
      "arbeit_b": "<arbeit_b>",
      "grund_b": "<grund_b>",
      "bonus_b": "<bonus_b>",
      "wechselkosten": "<wechselkosten>"
    },
    "name": "stromtarife_bonus_vergleichen"
  }
}

Input Schema

NameRequiredDescriptionDefault
bonus_aYesEinmaliger Bonus A in Euro, soweit die Bedingungen erfüllt sind.
bonus_bYesEinmaliger Bonus B in Euro, soweit die Bedingungen erfüllt sind.
grund_aYesGrundpreis A in Euro pro Jahr.
grund_bYesGrundpreis B in Euro pro Jahr.
arbeit_aYesArbeitspreis A als Brutto-€/kWh.
arbeit_bYesArbeitspreis B als Brutto-€/kWh.
wechselkostenYesEinmalige Zusatzkosten für B in Euro.
jahresverbrauch_kwhYesErwarteter Jahresverbrauch in kWh.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

With readOnlyHint=true and openWorldHint=false, the safety profile is already carried by the annotations, so the bar for the description is lower. It adds that the comparison folds in one-time incentives, switching costs and follow-on costs, which is useful behavioral context. It still does not reveal the shape of the result (for example total annual cost per tariff or the savings figure), which matters for an unpaginated compute tool that has no output schema.

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 short sentences with the core action front-loaded and nothing wasted on filler. The only minor inefficiency is that the English sentence simply restates the German one, adding no information an agent does not already have.

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 read-only calculation tool with eight mandatory parameters and no output schema, the description covers the input side adequately but says nothing about what the result looks like — per-tariff annual totals, a difference, or a recommendation. That omission is the main gap relative to the tool's complexity.

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

Parameters4/5

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

Schema description coverage is 100% and every parameter is documented in German with units and bounds, so the schema carries the burden and the baseline of 3 is easily met. The description goes one step beyond by grouping bonuses, switching costs and recurring costs into the comparison, which helps an agent understand the roles of the fields rather than only their types.

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 gives a specific verb (compare/vergleichen) and resource (two electricity offers) and names the cost components it works with: bonuses, switching costs and recurring costs. That is enough to distinguish it from the sibling calculators, though it does not name any sibling explicitly.

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 intended use — comparing exactly two tariffs across a year's consumption — is implied by the wording and by the eight required parameters. However, there is no explicit when-to-use guidance, no mention of when a single-tariff or non-bonus comparison would be the better route, and no prerequisites 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