Skip to main content
Glama

getecoback-climate-weather

wasserhistorie_sperrzeit_nachlauf_pruefung

Read-only

Dokumentierte Nichtverfügbarkeit einer Verbrauchsstelle vom gemessenen Wasserbedarf nach Rückkehr trennen — Distinguish deferred water use from remembered use during an unavailable window.

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": {
      "ausfall_l": "<ausfall_l>",
      "sonstige_l": "<sonstige_l>",
      "nachher_l": "<nachher_l>",
      "nachgeholt_l": "<nachgeholt_l>"
    },
    "name": "wasserhistorie_sperrzeit_nachlauf_pruefung"
  }
}

Input Schema

NameRequiredDescriptionDefault
ausfall_lYesGemessenes Zählervolumen des Zeitfensters ohne nutzbare betrachtete Zapfstelle.
nachher_lYesGesamtvolumen im anschließenden Fenster.
sonstige_lYesEindeutig anderen Stellen zugeordnete gemessene Liter im Ausfallfenster.
nachgeholt_lYesDavon direkt gemessene, nachgewiesenermaßen nachgeholte Entnahmen.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.6/5.0
Behavior2/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 known without the description. Beyond that, the description adds only abstract framing and says nothing about the result form, how tolerance or rounding is handled, or what happens with inconsistent inputs — notable since there is no output schema to fall back on.

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 core distinction front-loaded; nothing is padded. The bilingual restatement is arguably redundant but the English rendering genuinely aids comprehension of the terse German term, so it mostly earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With four required numeric inputs, no output schema, and no annotations describing results, the description should explain what the calculation produces and how to interpret it. It instead stops at the conceptual distinction, leaving the agent unable to predict or use the return value.

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%: all four litre parameters carry their own German definitions, so the schema already does the semantic work. The description mentions the measured-versus-remembered distinction but adds no parameter-level detail (units, typical magnitudes, relationship between ausfall_l, sonstige_l and nachgeholt_l) beyond what is already structured. Baseline 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific operation ('trennen'/distinguish deferred water use from remembered use during an unavailable window) applied to a specific resource (measured water demand at a consumption point). However, it stays at the conceptual level: an agent cannot tell from the text whether this tool computes a residual volume, returns a boolean plausibility check, or flags an inconsistency, and there is no differentiation from the many similarly-named sibling tools. Purpose is inferable but vague.

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

Usage Guidelines2/5

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

There is no statement of when to call this tool, what preconditions the four measurements must satisfy, or which alternative sibling tool to use when the situation differs. The text only describes the concept, leaving the selection decision entirely to inference.

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