Skip to main content
Glama

getecoback-raumklima

stromhistorie_spaete_ablesung_versionsfolge

Read-only

Für einen bereits abgeschlossenen Zeitraum als vorläufig und bestätigt abgelegte Zählerwerte zeitlich rekonstruieren — Identify the value available at a historical report cutoff versus a later validated reading.

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": {
      "verwendeter_kwh": "<verwendeter_kwh>",
      "bestaetigt_kwh": "<bestaetigt_kwh>",
      "korrektur_eingang_tag": "<korrektur_eingang_tag>",
      "bericht_stichtag": "<bericht_stichtag>",
      "zeitraum_identisch": "<zeitraum_identisch>"
    },
    "name": "stromhistorie_spaete_ablesung_versionsfolge"
  }
}

Input Schema

NameRequiredDescriptionDefault
bestaetigt_kwhYesSpäter validierter Verbrauchswert für genau dasselbe Fenster.
verwendeter_kwhYesFür das Fenster damals verfügbarer vorläufiger Verbrauchswert.
bericht_stichtagYesTag des abzubildenden Berichts, ab demselben Tag 0.
zeitraum_identischYesBeide Angaben verwenden dieselben Messgrenzen und dasselbe Register?
korrektur_eingang_tagYesTag des dokumentierten Eingangs der Bestätigung, ab gemeinsamem Tag 0.

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?

The read-only and closed-world annotations already cover the safety profile, while the description adds the useful conceptual model of provisional versus later validated readings at a cutoff. However, it does not explain behavior when the two readings are not for identical windows or how corrections affect the reconstruction.

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?

The definition is short and front-loads the core reconstruction task before the cutoff-versus-validated distinction. The bilingual restatement is slightly redundant but still efficient overall.

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 tool with no output schema, the description explains the conceptual purpose but does not describe the return shape or the meaning of a result when 'zeitraum_identisch' is false. It is adequate but leaves some interpretive work to the caller.

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%, so all five parameters already have documented meaning in the input schema. The description reinforces the provisional-versus-confirmed distinction but adds no parameter-specific syntax, constraints, or interpretation 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 states a specific verb and resource: reconstructing stored provisional and confirmed meter values for an already completed period, and distinguishing the value available at a historical report cutoff from a later validated reading. This is much clearer than a tautological restatement, though it does not explicitly distinguish the tool from any named sibling.

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?

It indicates the relevant context ('für einen bereits abgeschlossenen Zeitraum') and the analytical question the tool answers, but it gives no explicit when-not conditions and does not name an alternative tool or comparison case.

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