Skip to main content
Glama

getecoback-climate-weather

stromschaetzung_abweichung

Read-only

Einen geschätzten Ablesewert mit einem Stand vom selben Datum abgleichen. — Quantify the difference between an estimated bill reading and a contemporaneous actual reading.

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": {
      "vorher_kwh": "<vorher_kwh>",
      "geschaetzt_kwh": "<geschaetzt_kwh>",
      "tatsaechlich_kwh": "<tatsaechlich_kwh>",
      "arbeit": "<arbeit>"
    },
    "name": "stromschaetzung_abweichung"
  }
}

Input Schema

NameRequiredDescriptionDefault
arbeitYesKonstanter Arbeitspreis in Brutto-€/kWh.
vorher_kwhYesLetzter bestätigter Startwert desselben Zählers.
geschaetzt_kwhYesGeschätzter Endstand auf der Abrechnung.
tatsaechlich_kwhYesTatsächlich abgelesener Stand am selben Enddatum.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered and the description only needs to add context. It does add the important domain constraint that the two readings must belong to the same date, but it never says what actually gets computed — a kWh delta, a percentage, or a monetary correction using the Arbeitspreis — which is the key behavioral question here.

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

Conciseness3/5

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

The definition is short and front-loads the action, but it is the same sentence stated twice (German then English), so half of the text is pure duplication rather than added information. No waste beyond that, but no structure that helps the agent either.

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

Completeness2/5

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

With no output schema, the description carries the burden of explaining what comes back, and it does not: the return could be a kWh difference, a rounded estimate, or a €-amount derived from arbeitspreis. Combined with zero guidance on the sign/direction of the difference or on the meaning of the confirmed start value, an agent cannot predict the result of invoking it.

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 four parameters (vorher_kwh, geschaetzt_kwh, tatsaechlich_kwh, arbeit) are already documented in the schema and the baseline of 3 applies. The description only echoes the two reading values and says nothing about the Arbeitspreis parameter, which is the one that likely drives a cost-based result.

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 uses a specific verb and resource — 'Einen geschätzten Ablesewert mit einem Stand vom selben Datum abgleichen' / 'quantify the difference between an estimated bill reading and a contemporaneous actual reading' — so an agent knows it computes the gap between two readings. It never names or distinguishes itself from any sibling (e.g. energielabel_messwert_abgleichen), so the differentiation component is missing.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no statement of prerequisites (e.g. that both readings must share the same end date, or that a confirmed previous value is required), and no mention of alternatives. The description only says what the tool does, leaving the agent to infer whether this is the right tool for a correction/estimate dispute scenario.

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