Skip to main content
Glama

getecoback-climate-weather

duschstart_wasseraufteilung_start_zweck_ablauf

Read-only

Gemessenen Anlauf einer Dusche zwischen separat genutztem und nicht aufgefangenem Wasser aufteilen — Reconcile measured run-up, secondary use and uncaptured water.

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": {
      "gesamt_anlauf_l": "<gesamt_anlauf_l>",
      "genutzt_l": "<genutzt_l>",
      "noch_im_gefaess_l": "<noch_im_gefaess_l>",
      "spaeter_abgeleitet_l": "<spaeter_abgeleitet_l>",
      "gleiche_entnahme": "<gleiche_entnahme>"
    },
    "name": "duschstart_wasseraufteilung_start_zweck_ablauf"
  }
}

Input Schema

NameRequiredDescriptionDefault
genutzt_lYesAufgefangene Menge, die tatsächlich für den vorgesehenen anderen Zweck eingesetzt wurde.
gesamt_anlauf_lYesGesamte gemessene Anlaufmenge derselben Entnahme.
gleiche_entnahmeYesGehören alle Mengen zur gleichen gemessenen Entnahme?
noch_im_gefaess_lYesAufgefangener Anteil, der zum Protokollstichtag noch im Gefäß war.
spaeter_abgeleitet_lYesZuerst aufgefangenes und anschließend ohne andere Nutzung abgegebenes Wasser.

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 establish readOnlyHint=true and openWorldHint=false; the description adds that the operation is an allocation/reconciliation of measured quantities rather than a simple read. It does not disclose validation rules, error behavior for inconsistent amounts, or what is returned, so it adds only moderate context beyond annotations.

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 short, front-loaded sentence pair with the German statement followed by an English equivalent. The bilingual duplication is slightly redundant but not verbose, and the core operation is immediately clear.

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 five-parameter reconciliation tool with no output schema, the description establishes the conceptual model but omits the expected return values, the role of 'gleiche_entnahme' in validation, and any sum or invariant rules. Those omissions leave the definition less complete than the parameter count and calculation nature warrant.

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 five parameters are documented in the schema, including the same-extraction boolean and quantity bounds. The description only maps them loosely to secondary use and uncaptured water; it adds no syntax or constraint detail beyond the schema, so baseline 3 is appropriate.

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?

States a specific computational verb ('aufteilen'/'Reconcile') and resource ('gemessenen Anlauf einer Dusche'), and names the allocation categories (separately used vs uncaptured water). It does not explicitly distinguish itself from shower-related siblings, so it is clear but not fully differentiated.

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 description implies the scenario (reconciling a measured shower run-up) but gives no explicit when-to-use, when-not-to-use, or alternative tool guidance. It is enough to infer the basic context, but nothing more.

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