Skip to main content
Glama

getecoback-climate-weather

wasserzaehler_anzeigeumlauf

Read-only

Verbrauch über einen dokumentierten Umlauf derselben Wasserzähleranzeige bestimmen — Recover water volume across one verified counter rollover.

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_liter": "<start_liter>",
      "ende_liter": "<ende_liter>",
      "umlauf_liter": "<umlauf_liter>",
      "protokoll": "<protokoll>"
    },
    "name": "wasserzaehler_anzeigeumlauf"
  }
}

Input Schema

NameRequiredDescriptionDefault
protokollYesWas bestätigt das Ableseprotokoll für dasselbe Gerät?
ende_literYesLetzte Anzeige in Litern.
start_literYesErste Anzeige in Litern.
umlauf_literYesVom Hersteller dokumentierter voller Anzeigezyklus in Litern, bis die Anzeige wieder null zeigt.

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 without the description's help. Beyond that, the description discloses nothing about how the volume is computed, what happens when 'protokoll' is 'unbekannt', or whether an ambiguous rollover is rejected. With annotations lowering the bar, this is adequate but thin for a calculation tool.

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 that leads with the operative constraint ('documented rollover of the same display'). The bilingual duplication adds length without new information, but nothing is padded or buried, and the core intent is readable in the first clause.

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?

Four required numeric/enum parameters and no output schema mean the description should say what is returned (presumably consumed liters) and how edge cases are handled. Neither is present, and the 'unbekannt' branch of the protocol enum is left unexplained. It is sufficient to start a call but not to predict its 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%, so all four parameters — start_liter, ende_liter, umlauf_liter, and the protokoll enum — are already documented in the schema. The description adds no syntax, units, or interpretation beyond that, so the baseline 3 applies. It misses the chance to explain the meaning of the enum values relative to the computation.

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 specific operation on a specific resource: determining consumption across one documented rollover of the same water-meter display. A 'recover water volume across one verified counter rollover' phrasing makes the computation recognizable and separates it from the sibling that classifies the meter's resting state. It stops short of 5 because the German and English halves simply restate each other rather than naming the sibling it is not.

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 rollover scenario is embedded in the purpose, so an agent can infer this is the tool for a reading interval that wrapped past zero. However, there is no explicit when-to-use or when-not guidance, no mention of the 'unbekannt' protocol case, and no pointer to an alternative for intervals without a rollover. Usage is implied rather than stated.

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