Skip to main content
Glama

getecoback-raumklima

duschwasserbudget_zwei_personen

Read-only

Gemeinsames Duschwasserbudget auf zwei selbst vorgegebene Mindestzeiten und gleiche Zusatzzeit verteilen — Allocate a shared water allowance when two showers have different measured flow rates.

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>",
      "a_l_min": "<a_l_min>",
      "b_l_min": "<b_l_min>",
      "a_mindest_min": "<a_mindest_min>",
      "b_mindest_min": "<b_mindest_min>"
    },
    "name": "duschwasserbudget_zwei_personen"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_l_minYesGemessener Durchfluss an Dusche A in Litern je Minute.
b_l_minYesGemessener Durchfluss an Dusche B in Litern je Minute.
budget_lYesVerfügbares gemeinsames Wasserbudget in Litern.
a_mindest_minYesSelbst gewählte Mindestzeit A in Minuten.
b_mindest_minYesSelbst gewählte Mindestzeit B in Minuten.

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, closed-world calculation. The description adds the core allocation rule — two self-set minimum times plus an equal additional-time share — but does not disclose what is returned, what happens if the budget cannot cover both minimums, or how rounding is handled. This is useful behavioral context but incomplete.

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 definition is compact and front-loads the action and allocation rule. The bilingual duplication is mildly redundant, and the English sentence is less precise than the German one, but neither consumes much space.

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 fully documented required parameters and read-only annotations, the description covers the purpose and main allocation concept. However, there is no output schema and the description does not say what the tool returns — for example, allocated minutes or liters per shower — or how infeasible budgets are handled, which is a material gap for a calculation 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?

All five parameters have complete schema descriptions with types, ranges, and units, so the schema already carries the parameter documentation burden. The description reinforces the budget, flow-rate, and minimum-time concepts but adds no formula or syntax detail beyond the schema. The baseline score 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 names a specific operation: distributing a shared shower-water budget across two showers with individually chosen minimum times and an equal additional-time share. It is clearly distinct from unrelated household-calculation siblings, though it does not explicitly contrast with any similar shower tool.

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 English clause gives a scenario — two showers with different measured flow rates — that implies when to use the tool, but there is no explicit when-not-to-use guidance or named alternative. An agent can infer the context but must guess whether another tool is more appropriate for equal flow rates or single-shower planning.

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