Skip to main content
Glama

getecoback-raumklima

stromexport_gerundete_bloecke_summieren

Read-only

Eine Summe einzeln gerundeter Verbrauchsblöcke gegen einen unabhängigen Gesamtzähler prüfen — Audit the accumulated rounding range in a block energy export.

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": {
      "bloecke": "<bloecke>",
      "summe_wh": "<summe_wh>",
      "rundungsschritt_wh": "<rundungsschritt_wh>",
      "gesamt_wh": "<gesamt_wh>",
      "gesamt_spielraum_wh": "<gesamt_spielraum_wh>"
    },
    "name": "stromexport_gerundete_bloecke_summieren"
  }
}

Input Schema

NameRequiredDescriptionDefault
bloeckeYesZahl separat gerundeter, gleich aufgelöster Blöcke.
summe_whYesSumme der separat gerundeten Energieblöcke in Wh.
gesamt_whYesUnabhängig gemeldeter Gesamtwert für exakt dieselben Blöcke in Wh.
rundungsschritt_whYesExportstufe in Wh; Rundung auf die nächste Stufe vorausgesetzt.
gesamt_spielraum_whYesBelegter maximaler Fehler des Gesamtwerts in Wh.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/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 that this is a cross-check of a computed sum against an independently reported total within a documented error margin ('gesamt_spielraum_wh'), which is useful behavioral context. However, it does not state what happens on mismatch, whether a tolerance breach is reported or thrown, or what the caller receives — leaving the core behavioral question unanswered for a validation tool.

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?

One sentence, front-loaded with the operation and its object, with no filler. The only waste is the near-duplicate German/English rendering, which adds length without adding 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?

Five required numeric parameters with no output schema means the description should explain the return value — pass/fail, excess in Wh, or a range verdict — and it does not. It does convey the conceptual model adequately (rounded block sum compared against a total with a stated error allowance), so an agent can call it, but the outcome semantics remain unspecified.

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%, so the schema already explains every parameter, including the rounding step and the total's error allowance. The description reinforces the roles of the two compared values (block sum vs. independent total) and the accumulated-rounding framing, which orients the agent without contradicting the schema. Baseline 3 is exceeded slightly because the description ties the parameters into one coherent audit concept.

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 ('prüfen'/summieren) and concrete resources: a sum of individually rounded consumption blocks checked against an independent total meter. It is clearly distinct from the sibling overlap/metadata tools. It loses a point because the bilingual phrasing ('Eine Summe ... prüfen — Audit the accumulated rounding range') is compressed and the German and English halves emphasize slightly different actions (summing vs. auditing).

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 explicit when-to-use or when-not-to-use guidance, and no alternative sibling is named. An agent must infer from context that this applies only to block energy exports with per-block rounding. The word 'Audit' hints at a validation scenario but does not define the conditions that select this tool over e.g. stromexport_einheit_metadaten_abgleichen.

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