Skip to main content
Glama

getecoback-climate-weather

handspuelen_becken_und_hahn_mengenbilanz

Read-only

Beim selben Handspülvorgang Beckenfüllungen und zusätzliche laufende Entnahmen ohne Doppelerfassung addieren — Combine recorded basin fill and separate tap use without overlap.

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": {
      "becken_gefuellt_l": "<becken_gefuellt_l>",
      "hahn_gesamt_l": "<hahn_gesamt_l>",
      "becken_aus_diesem_hahn_l": "<becken_aus_diesem_hahn_l>",
      "auswertung_vollstaendig": "<auswertung_vollstaendig>"
    },
    "name": "handspuelen_becken_und_hahn_mengenbilanz"
  }
}

Input Schema

NameRequiredDescriptionDefault
hahn_gesamt_lYesGesamte gemessene Hahnmenge desselben protokollierten Vorgangs in Litern.
becken_gefuellt_lYesSumme aller gemessenen Beckenfüllungen in Litern.
auswertung_vollstaendigYesErfasst das Protokoll alle benutzten Wasserquellen für diesen Vorgang?
becken_aus_diesem_hahn_lYesAnteil der Beckenfüllungen, der schon in der Hahnmenge gezählt ist.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already declare that this is a read-only, non-open-world operation. The description adds that the tool combines quantities without overlap, but it does not explain how incomplete data is handled or what the returned result represents.

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?

The description is short and front-loads the core operation. The bilingual duplication is mildly redundant, but it does not obscure the main point.

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?

For a four-parameter calculation tool with no output schema, the description covers the core aggregation but leaves important gaps: it does not state the return value or the behavior when 'auswertung_vollstaendig' is false. These gaps are significant but less severe because annotations and parameter descriptions are otherwise rich.

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 the parameter semantics are already documented in the schema. The description reinforces the no-overlap idea but does not add formula details or other meaning beyond what the schema provides.

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 gives a specific verb and resources: add basin fillings and additional running tap withdrawals for the same handwashing process without double counting. It is clear what the tool does, but it does not explicitly distinguish itself from any sibling tool.

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

Usage Guidelines4/5

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

The description establishes a clear usage context: the quantities must belong to the same handwashing process. It does not state when not to use the tool or name any alternative, so it falls short of full when/when-not guidance.

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