Skip to main content
Glama

getecoback-raumklima

brause_duschdauer_wasser_und_waerme_limit

Read-only

Längere Dusche nach Brausenwechsel gegen den bisherigen Wasser- und Wärmeverbrauch gleichzeitig abgleichen — Find a comparable shower duration that keeps both water and heat within the old use.

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": {
      "vorher_l_min": "<vorher_l_min>",
      "vorher_min": "<vorher_min>",
      "vorher_delta_k": "<vorher_delta_k>",
      "nachher_l_min": "<nachher_l_min>",
      "nachher_delta_k": "<nachher_delta_k>"
    },
    "name": "brause_duschdauer_wasser_und_waerme_limit"
  }
}

Input Schema

NameRequiredDescriptionDefault
vorher_minYesBeobachtete Duschdauer vorher in Minuten.
vorher_l_minYesGemessener Durchfluss vorher, Liter pro Minute.
nachher_l_minYesGemessener Durchfluss der neuen Brause, Liter pro Minute.
vorher_delta_kYesDifferenz von Kalt- zu Mischwasser vorher, Kelvin.
nachher_delta_kYesDifferenz von Kalt- zu Mischwasser im neuen Szenario, Kelvin.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare this a pure, closed-world read/compute operation, so the safety profile is covered. The description adds the meaningful constraint that both water and heat must simultaneously stay within the old baseline, which is a joint-feasibility behavior worth knowing. However, it never states what happens if no such duration exists, whether the result is a cap or a point estimate, or the units of the answer.

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?

The definition is a single short sentence, which is well sized, and the constraint that both resources must stay within the old consumption is front-loaded. But the German sentence and its English restatement are largely duplicative, and neither states the returned quantity or the failure mode, so the space is not fully earned.

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?

With five required numeric parameters, no output schema, and no nested structures, the description needs to carry the result semantics itself. It conveys the goal but omits what a caller gets back and whether infeasible inputs (e.g. the new head already exceeding baseline) are rejected or clamped, leaving a real gap for a computational tool.

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% and each of the five required parameters carries its own German description with units and bounds, so the schema does the heavy lifting and a 3 baseline applies. The description merely alludes to the two domains (water volume and heat) without adding syntax, coupling, or validity constraints beyond what the schema states.

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 names a concrete operation on a concrete resource: reconcile a longer shower duration after a shower-head swap against the previous water and heat consumption, with the English gloss clarifying the goal of finding a comparable duration that stays within old levels. It is distinguishable from siblings like brause_fliessdruck_bereich or brauseschlauch_anschluesse_abgleichen, which do not compute a duration limit. It stops short of 5 because the description never says the tool returns a duration limit as its result rather than, say, a comparison report.

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?

Usage is only implied through the phrase 'nach Brausenwechsel' and the constraint 'keeps both water and heat within the old use' — an agent can infer this is for evaluating a new shower head against a baseline. There is no explicit when-to-use/when-not statement and no named alternative for related shower calculations among the siblings.

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