Skip to main content
Glama

getecoback-raumklima

warmwasser_warteverlust

Read-only

Wasserbedarf während der Wartezeit bis zum warmen Duschwasser schätzen — Estimate the water drawn before warm water reaches the shower.

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": {
      "flow_l_min": "<flow_l_min>",
      "wait_seconds": "<wait_seconds>",
      "times_per_year": "<times_per_year>",
      "water_eur_m3": "<water_eur_m3>"
    },
    "name": "warmwasser_warteverlust"
  }
}

Input Schema

NameRequiredDescriptionDefault
flow_l_minYesGemessener Durchfluss während der Wartezeit in l/min.
wait_secondsYesZeit bis zur gewünschten Temperatur in Sekunden.
water_eur_m3YesMengenabhängiger Wasser- und Abwasserpreis in EUR/m³.
times_per_yearYesVergleichbare Starts pro Jahr.

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?

The annotations already establish that this is a read-only, non-open-world calculation. The description adds that the result is an estimate of water drawn before warm water arrives, but it does not explain assumptions, calculation logic, or whether the output covers volume, cost, or annualized values.

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 purpose. The German and English versions duplicate the same content, which is slightly redundant but not materially wasteful.

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 read-only calculator with no output schema, the description states the core estimate but does not specify what the returned value represents, such as liters per event, annual water volume, or cost. That leaves a meaningful gap for correct interpretation of results.

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 coverage is 100%, and the parameter descriptions already explain flow, wait time, annual starts, and water price. The tool description adds no parameter-specific meaning beyond the schema, so the baseline of 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?

The description gives a clear verb (schätzen/estimate) and resource (water drawn before warm water reaches the shower). It is distinguishable from measurement-oriented siblings by framing the result as an estimate, but it does not explicitly name which sibling to use instead.

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 use case: estimating shower water wasted while waiting for warm water. It does not state when not to use it or point to alternatives such as duschdurchfluss_messen or duschwasser_mischverhaeltnis, so guidance remains implicit.

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