Skip to main content
Glama

getecoback-raumklima

stromzaehler_doppelregister_abgleichen

Read-only

Verbrauch zweier Bezugstarifregister mit dem Gesamtregister abgleichen. — Cross-check two import tariff registers against the total register.

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": {
      "tarif_a_kwh": "<tarif_a_kwh>",
      "tarif_b_kwh": "<tarif_b_kwh>",
      "gesamt_kwh": "<gesamt_kwh>",
      "toleranz_kwh": "<toleranz_kwh>"
    },
    "name": "stromzaehler_doppelregister_abgleichen"
  }
}

Input Schema

NameRequiredDescriptionDefault
gesamt_kwhYesVerbrauchsdifferenz des Gesamtbezugsregisters in kWh.
tarif_a_kwhYesVerbrauchsdifferenz des ersten Bezugstarifregisters in kWh.
tarif_b_kwhYesVerbrauchsdifferenz des zweiten Bezugstarifregisters in kWh.
toleranz_kwhYesZulässige Rundungsdifferenz in kWh.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/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. The description adds the cross-check framing but never states what happens when the registers fall outside toleranz_kwh — whether it reports a discrepancy, throws, or returns a boolean — which is the behavior an agent most needs. Given annotated coverage, a 3 is fair.

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 purpose front-loaded and no filler. The German and English renderings are fully redundant, which costs a little space but keeps the intent unambiguous.

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, four-parameter check with no output schema, the definition is adequate but thin: the caller still cannot predict whether the result is a pass/fail verdict, a delta, or an error on breach. Naming the outcome shape would close the remaining gap.

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%, with each of the four parameters documented including units (kWh) and bounds, so the baseline is 3. The description supplies the comparison framing that the schema lacks, but does not explain the arithmetic relationship (tarif_a + tarif_b versus gesamt) or 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 (abgleichen/cross-check) and concrete resources (two Bezugstarifregister versus the Gesamtregister), so the operation is unmistakable. It stops short of distinguishing itself from the numerous other *_abgleichen siblings, leaving the agent to infer selection from subject matter alone.

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 statement of when to use this tool versus alternatives, no prerequisites, and no exclusion criteria. The reader must infer from the name that it is a validation step after register readings are captured.

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