Skip to main content
Glama

getecoback-raumklima

stromprotokoll_lueckensumme_anker

Read-only

Fehlende Intervallwerte über einen passenden kumulierten Gesamtanker mengenmäßig eingrenzen — Recover only the aggregate energy of missing bins from a matched reference total.

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": {
      "gesamt_wh": "<gesamt_wh>",
      "vorhanden_wh": "<vorhanden_wh>",
      "anker_fehler_wh": "<anker_fehler_wh>",
      "intervalle_fehler_wh": "<intervalle_fehler_wh>",
      "grenzen_passend": "<grenzen_passend>"
    },
    "name": "stromprotokoll_lueckensumme_anker"
  }
}

Input Schema

NameRequiredDescriptionDefault
gesamt_whYesGesamtverbrauch aus zwei Ankerständen über alle Zielintervalle in Wh.
vorhanden_whYesSumme der lückenlos belegten einzelnen Intervallwerte in Wh.
anker_fehler_whYesMaximaler Fehler der Gesamtmessung in Wh.
grenzen_passendYesSind Zählerumfang, Zeitgrenzen und überschneidungsfreie vorhandene Intervalle bestätigt?
intervalle_fehler_whYesMaximaler Fehler der Summe der vorhandenen Intervalle in Wh.

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 safety is covered. The description adds one genuinely useful behavioral fact — that the result is aggregate-only, not a per-bin reconstruction — but says nothing about how the error bounds are combined or what form the constrained result takes.

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?

A single bilingual sentence with the scope limitation front-loaded in the German clause and the key constraint ('only the aggregate') repeated in English. No filler; the bilingual restatement is defensible for a jargon-dense domain, though it does not add new 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?

With no output schema, the description carries the burden of describing the return value, and it only hints that an aggregate energy for the missing bins comes back — it does not state whether the result is a point estimate, an interval, or how the error terms propagate. For a five-required-parameter computation tool with no output schema, that is an important omission.

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 each of the five parameters carries a precise German description including units (Wh) and bounds, so the schema does the heavy lifting. The description only loosely maps 'matched reference total' to the anchor parameters and 'missing bins' to vorhanden_wh, adding no syntax or constraint detail beyond the schema.

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 operation (bounding/constraining missing interval values) against a specific resource (a matched cumulative reference total), and adds the crucial scope qualifier 'only the aggregate energy of missing bins' — i.e. it does not reconstruct individual bins. That distinguishes it from per-interval reconstruction siblings, though it never names an alternative 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?

Usage is only implied: the phrase 'über einen passenden kumulierten Gesamtanker' signals that a matched anchor total must exist before this applies, which corresponds to the required 'grenzen_passend' flag. There is no explicit statement of when to prefer this tool over a per-interval recovery approach, and no when-not guidance.

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