Skip to main content
Glama

getecoback-climate-weather

wasserverlauf_erste_spuelung_verbrauchsdosis

Read-only

Bei einer protokollierten Folge kurzer Zapfungen eine anfängliche Spülmenge nur einmal auf die tatsächlich erledigten Nutzungen beziehen — Separate one documented initial purge from later water draws.

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": {
      "gesamtliter": "<gesamtliter>",
      "anfangs_liter": "<anfangs_liter>",
      "abgeschlossene_nutzungen": "<abgeschlossene_nutzungen>",
      "entnahmen_auswertbar": "<entnahmen_auswertbar>"
    },
    "name": "wasserverlauf_erste_spuelung_verbrauchsdosis"
  }
}

Input Schema

NameRequiredDescriptionDefault
gesamtliterYesGemessene Wassermenge der vollständigen Folge.
anfangs_literYesDirekt gemessene einmalige Spülmenge vor den Nutzungen.
entnahmen_auswertbarYesSind keine weiteren Vorläufe, Unterbrechungen oder unvollständigen Nutzungen im Gesamtwert enthalten?
abgeschlossene_nutzungenYesZahl der vollständig in der Folge erledigten, vergleichbaren Nutzungen.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile and closed-world nature are covered structurally; the description adds only that a purge is counted once, which is a computation rule rather than behavior. It says nothing about the result shape, units, or edge-case handling (e.g. what happens when abgeschlossene_nutzungen is 1), which no annotation covers.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, brief and front-loaded with the condition, but the German sentence and the English sentence are near-verbatim restatements rather than complementary information, so half the text adds no new content.

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?

This is a four-required-parameter computation tool with no output schema, so the description carries the burden of explaining the returned value — and it does not: an agent cannot tell whether the result is a per-use litre figure, a remainder, or a flag. For a tool whose sole purpose is producing a derived number, that is a substantive gap.

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 are fully documented in the schema and the baseline of 3 applies. The description adds no mapping between its 'anfängliche Spülmenge' / 'erledigte Nutzungen' language and the parameters anfangs_liter and abgeschlossene_nutzungen, and never mentions entnahmen_auswertbar at all.

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 does convey a specific operation — separating a one-time initial purge volume from later draws and charging it against completed uses — but the operative verb ('beziehen' / 'separate') is abstract and never states what the tool actually returns (a per-use dose?). No sibling is named or contrasted, so an agent cannot position it among the many other water/draw tools from the definition alone.

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?

A triggering condition is implied ('bei einer protokollierten Folge kurzer Zapfungen'), which is more than nothing, but there is no explicit when-not guidance, no prerequisites (e.g. that draws must be comparable and complete), and no alternative tool named for the case where no initial purge exists.

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