Skip to main content
Glama

getecoback-climate-weather

spuelgesamtanzeige_intervall_geraetewechsel_beleg

Read-only

Zwei Gesamtanzeigen nur beim belegten selben physikalischen Gerät und fortlaufendem Zählerstand vergleichen — Avoid subtracting lifetime displays across replacement units.

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": {
      "anfang_l": "<anfang_l>",
      "schluss_l": "<schluss_l>",
      "selbes_einzelgeraet": "<selbes_einzelgeraet>",
      "anzeige_fortlaufend": "<anzeige_fortlaufend>",
      "einheit_und_gesamtfeld": "<einheit_und_gesamtfeld>"
    },
    "name": "spuelgesamtanzeige_intervall_geraetewechsel_beleg"
  }
}

Input Schema

NameRequiredDescriptionDefault
anfang_lYesBelegter erster Gesamt-Literwert in Informationen.
schluss_lYesBelegter zweiter Gesamt-Literwert in Informationen.
anzeige_fortlaufendYesUnveränderte Zählergrundlage zwischen den Ablesungen unabhängig belegt?
selbes_einzelgeraetYesDasselbe einzelne Gerät jenseits desselben Modellnamens bestätigt?
einheit_und_gesamtfeldYesBeide Werte stammen aus dem gleichen Gesamtfeld und sind in Litern erfasst.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/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 description only needs to add domain behavior – and it does add a meaningful caveat about not diffing lifetime displays across replacement units. However, it does not say what the tool returns (a difference? a comparison verdict?) nor how it behaves when the confirmation booleans are false, which matters because there is no output schema.

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 compact clauses with the operation front-loaded and the validity constraint immediately after; the English clarifier reinforces rather than repeats. The mixed German/English phrasing is slightly inelegant but costs almost nothing in length.

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, no-output-schema tool the definition covers the gating logic well and annotations cover the safety profile. It remains incomplete on the return value and on the failure mode when 'selbes_einzelgeraet' or 'anzeige_fortlaufend' are false, which an agent cannot infer from the structured fields.

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 its own German description, so the schema does the semantic work. The description gestures at the same concepts (same device, continuous counter) but adds no format, range, or ordering detail beyond the schema's 0–1,000,000 bounds.

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 – comparing two cumulative ('Gesamt') readings – and immediately binds it to two validity conditions (same physical device, continuous counter). It is clearly narrower than the sibling set (e.g. geraetewechsel_rechnen, stapelsaeule_einzelgeraetwechsel_alter_satz_neuer_beleg), though it does not name any sibling explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a positive precondition ('nur beim belegten selben physikalischen Gerät und fortlaufendem Zählerstand') and an implicit when-not via 'Avoid subtracting lifetime displays across replacement units'. What is missing is a pointer to what an agent should call instead when a device was replaced, so it stops short of full routing 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