Skip to main content
Glama

getecoback-climate-weather

wasserzaehler_ruhezustand_einordnen

Read-only

Zwei abgelesene Wasserzählerstände ohne geplante Entnahme einordnen — Interpret two observed water meter readings during a no-draw interval.

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": {
      "start_m3": "<start_m3>",
      "ende_m3": "<ende_m3>",
      "schritt_l": "<schritt_l>",
      "entnahmen_bekannt_aus": "<entnahmen_bekannt_aus>"
    },
    "name": "wasserzaehler_ruhezustand_einordnen"
  }
}

Input Schema

NameRequiredDescriptionDefault
ende_m3YesEndstand in Kubikmetern.
start_m3YesAnfangsstand desselben Wasserzählers in Kubikmetern.
schritt_lYesKleinster ablesbarer Schritt in Litern.
entnahmen_bekannt_ausYesWaren geplante und automatisch ausgelöste Wasserentnahmen im beobachteten Bereich ausgeschlossen?

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 interval must be draw-free, but it does not disclose what happens when entnahmen_bekannt_aus is false (error, caveat in result, or refusal) — a real gap for a required boolean gate.

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 bilingual sentence with no filler; the German and English halves say essentially the same thing, which is mild redundancy but useful for cross-language agents rather than padding.

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?

There is no output schema, so the description bears responsibility for indicating what an 'Einordnung' returns (a plausibility verdict? a leak suspicion? a classification label?), and it does not. The read-only annotation and full parameter docs keep this from being inadequate, but an agent cannot predict the shape or meaning of the result.

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 already carries a German description, so the schema does the heavy lifting. The description adds little beyond confirming both readings come from the same meter and belong to a no-draw interval; it gives no guidance on unit handling (m³ vs. schritt_l in litres) or on the semantics of the boolean.

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?

Names a specific resource (two observed water meter readings) and a specific operation (einordnen / interpret) constrained to a no-draw interval, which separates it from siblings like stromzaehler_stichtag_einordnen or the many *_einordnen tools. The verb 'einordnen' remains somewhat abstract about what kind of interpretation is produced, which keeps it off a 5.

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 phrase 'ohne geplante Entnahme' and the required parameter entnahmen_bekannt_aus imply the precondition for use (interval with planned draws excluded), but the description never states it explicitly as a when-to-use rule, nor does it name any alternative tool or say what to do when planned draws were not excluded.

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