Skip to main content
Glama

getecoback-climate-weather

stromablesung_mittleren_wert_korrigieren

Read-only

Einen korrigierten Zwischenstand in den beiden benachbarten Verbrauchsintervallen fortschreiben — Propagate one replaced historical meter reading into exactly two incident intervals.

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": {
      "frueher_kwh": "<frueher_kwh>",
      "spaeter_kwh": "<spaeter_kwh>",
      "fraglich_kwh": "<fraglich_kwh>",
      "ersetzt_kwh": "<ersetzt_kwh>",
      "selbes_register": "<selbes_register>"
    },
    "name": "stromablesung_mittleren_wert_korrigieren"
  }
}

Input Schema

NameRequiredDescriptionDefault
ersetzt_kwhYesDurch einen Beleg ersetzter Zwischenstand.
frueher_kwhYesBestätigter Stand vor der korrigierten Ablesung.
spaeter_kwhYesBestätigter Stand nach der korrigierten Ablesung.
fraglich_kwhYesBisher erfasster Zwischenstand.
selbes_registerYesAlle Stände demselben unveränderten Register zugeordnet?

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; the description adds the meaningful constraint that exactly two incident intervals are touched. It does not say what is returned (the two corrected interval values?), nor whether ordering/consistency of frueher/ersetzt/spaeter is validated or what happens on inconsistent input. Note the tension between a 'korrigieren/fortschreiben' framing and readOnlyHint=true; the description neither resolves nor clearly violates it, so no contradiction is flagged.

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, front-loaded sentence with the operative constraint ('exactly two incident intervals') stated up front. The German/English restatement is mild duplication, but it aids cross-lingual disambiguation rather than padding. Nothing extraneous beyond that.

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 five-required-parameter computation tool with no output schema, the definition should say what comes back and how the two intervals are derived; it instead only describes the intent. Annotations cover the safety dimension and the schema covers inputs, so the remaining gap is the result semantics and any validation/precondition rules (e.g. selbes_register must hold).

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 every parameter carries a German explanation, so the schema does the heavy lifting. The description only clarifies the relational intent (two confirmed boundary readings bracketing a replaced and a previously captured one) without adding formats, ordering constraints, or units beyond what the schema states. Baseline 3 applies.

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 states a concrete operation: carrying a corrected/replaced intermediate meter reading forward into exactly two adjacent consumption intervals, naming the inputs' roles (replaced vs. confirmed surrounding readings). It is specific enough that an agent knows this is a reading-correction propagation, not a general meter CRUD tool. It does not, however, relate itself to any named sibling, so differentiation comes only from the operation described.

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: you call it when a previously captured 'fraglich' reading has been superseded by a document-backed value and the two incident intervals must be recomputed. There is no explicit when-not guidance, no statement about what to do when more than two intervals are affected, and no alternative tool is named. An agent can infer the trigger but not the boundaries.

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