Skip to main content
Glama

getecoback-raumklima

spuelstatus_gesamtzaehler_programmmenge_laufnotizen

Read-only

Bei bestätigtem unverändertem Programmzähler Lücken in einer Liste abgeschlossener Läufe erkennen — Reconcile a documented run count against individual records.

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": {
      "zaehler_vorher": "<zaehler_vorher>",
      "zaehler_nachher": "<zaehler_nachher>",
      "eindeutige_notizen": "<eindeutige_notizen>",
      "zaehler_bedeutung_belegt": "<zaehler_bedeutung_belegt>",
      "einheitliche_zaehlerbasis": "<einheitliche_zaehlerbasis>"
    },
    "name": "spuelstatus_gesamtzaehler_programmmenge_laufnotizen"
  }
}

Input Schema

NameRequiredDescriptionDefault
zaehler_vorherYesAbgelesene Zahl vor dem Betrachtungsintervall.
zaehler_nachherYesAbgelesene Zahl danach.
eindeutige_notizenYesBestätigte unterschiedliche Liste abgeschlossener Läufe im Intervall.
zaehler_bedeutung_belegtYesDie genaue Zählerbedeutung entspricht den betrachteten abgeschlossenen Läufen.
einheitliche_zaehlerbasisYesDasselbe Gerät, derselbe Intervallbezug und gleicher Programmzähler belegt.

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 precondition that the program counter must be confirmed unchanged before reconciliation is valid, but it says nothing about what the reconciliation produces, how gaps are reported, or what happens when the preconditions fail to hold.

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, tightly front-loaded sentence with no filler. The bilingual German/English echo is somewhat redundant, but it hedges an opaque German tool name at low cost.

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 parameters and no output schema mean the description should say more about what a successful reconciliation returns (gap list, counts, verdict). The precondition and intent are covered, but the agent is left guessing at the result shape for a read-only analytical tool.

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 are already documented in the schema with bounds and meanings. The description adds only indirect meaning (the counter must be 'bestätigt unverändert', which ties to zaehler_bedeutung_belegt and einheitliche_zaehlerbasis) and no new syntactic or conditional detail; 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 names a concrete operation ('Lücken in einer Liste abgeschlossener Läufe erkennen / Reconcile a documented run count against individual records'), which is a specific verb plus object set rather than a restatement of the compound name. It does not, however, distinguish itself from the other spuelstatus_* siblings, so it is clear but not differentiated.

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?

The opening clause 'Bei bestätigtem unverändertem Programmzähler' gives a precondition for use, which implicitly tells the agent when this is the right choice. There is no explicit statement of when NOT to use it and no named alternative among the sibling tools.

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