Skip to main content
Glama

getecoback-raumklima

dusche_zeit_bei_wasserbudget

Read-only

Mit gemessenem Durchfluss die Zeit für ein Duschwasserbudget bestimmen — Find the shower time allowed by a personal water budget.

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": {
      "budget_l": "<budget_l>",
      "durchfluss_l_min": "<durchfluss_l_min>"
    },
    "name": "dusche_zeit_bei_wasserbudget"
  }
}

Input Schema

NameRequiredDescriptionDefault
budget_lYesBudget für gemischtes Duschwasser in Litern.
durchfluss_l_minYesGemessener Durchfluss bei üblicher Einstellung in Litern pro Minute.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered and the description need only add context. It does add that the flow rate should be a measured value ('gemessenem Durchfluss'), hinting at a measurement-first workflow, but says nothing about the result's unit or whether the budget refers to mixed water only.

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?

Two short sentences, front-loaded with the operative condition (measured flow rate) and free of padding. The bilingual restatement is mild redundancy but serves a clarification purpose rather than bloating the text.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter, read-only arithmetic tool with full schema coverage and no output schema, the definition supplies enough to call it correctly. The main omission is the unit/format of the computed result (presumably minutes), which the agent must infer.

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%, with both parameters bounded and documented (litres of mixed shower water, litres per minute at the usual setting), so the baseline of 3 applies. The description adds only the qualifier that the flow is measured, which the schema already conveys.

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 verb and resource: determine the shower duration permitted by a water budget given a measured flow rate. The German/English pairing makes the purpose unambiguous. It does not name a sibling such as duschdurchfluss_messen to delineate boundaries, so it stops short of a 5.

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 implied rather than stated: the agent can infer this is the tool for 'how long can I shower with X litres at Y l/min'. There is no explicit when-to-use, no exclusion of alternatives like duschdurchfluss_messen or duschwasser_mischverhaeltnis, and no mention of prerequisites such as obtaining the flow measurement first.

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