Skip to main content
Glama

getecoback-raumklima

stromrechnung_preisperioden_gegenprobe

Read-only

Gleich hohe Gesamtkilowattstunden auf vertauschte abgerechnete Preisperioden prüfen — Detect a possible swap of pre- and post-change invoice quantities.

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": {
      "mess_vor_kwh": "<mess_vor_kwh>",
      "mess_nach_kwh": "<mess_nach_kwh>",
      "rechnung_vor_kwh": "<rechnung_vor_kwh>",
      "rechnung_nach_kwh": "<rechnung_nach_kwh>",
      "toleranz_kwh": "<toleranz_kwh>"
    },
    "name": "stromrechnung_preisperioden_gegenprobe"
  }
}

Input Schema

NameRequiredDescriptionDefault
mess_vor_kwhYesBestätigter Verbrauch vor der Preisgrenze.
toleranz_kwhYesEigene Prüfspanne je Zeile, etwa wegen Anzeigerundung.
mess_nach_kwhYesBestätigter Verbrauch nach der Preisgrenze.
rechnung_vor_kwhYesVor der Preisgrenze abgerechnete Menge.
rechnung_nach_kwhYesNach der Preisgrenze abgerechnete Menge.

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?

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered and the description only needs to add context. It adds that this is a cross-check of equal total kWh against swapped periods, but says nothing about what a positive versus negative finding looks like or how the tolerance affects the verdict.

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 tight sentences, bilingual, with the core operation front-loaded and no filler. It is efficient, though the brevity borders on under-specification rather than maximal economy of information.

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?

There is no output schema, and the description does not state what the tool returns (a flag, a deviation, a boolean verdict), which is the main missing piece for a five-parameter comparison tool. Input meaning is fully carried by the schema, so the definition is adequate but not complete.

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% and all five parameters are documented in the schema, so the baseline of 3 applies. The description hints that measured (mess_*) values are compared against invoiced (rechnung_*) values across the price boundary, but adds no detail about how toleranz_kwh is applied.

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 verb and resource ("vertauschte abgerechnete Preisperioden prüfen" / detect a swap of pre- and post-change invoice quantities), so an agent knows exactly what is computed. It does not name or distinguish itself from the surrounding stromrechnung_* siblings, which keeps it below a 5.

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 check's purpose implies the situation in which it applies (a suspected swap between pre- and post-price-change quantities), but there is no explicit when-to-use statement, no exclusion, and no routing to alternatives such as the line-rounding or split-quantity siblings. Usage is only inferable from the purpose.

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