Skip to main content
Glama

getecoback-raumklima

sparbrause_kostenvergleich

Read-only

Zwei Duschdurchflüsse bei gleicher Zeit und Temperatur einschließlich Wasser und Wärme vergleichen — Compare shower-head scenarios including water and energy.

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": "<flow>",
      "newflow": "<newflow>",
      "minutes": "<minutes>",
      "count": "<count>",
      "cold": "<cold>",
      "warm": "<warm>",
      "factor": "<factor>",
      "price": "<price>",
      "water": "<water>",
      "cost": "<cost>"
    },
    "name": "sparbrause_kostenvergleich"
  }
}

Input Schema

NameRequiredDescriptionDefault
coldYesKaltwasser in °C.
costYesEinmalkosten in Euro.
flowYesBisherige Liter pro Minute.
warmYesGemischtes Duschwasser in °C.
countYesAnzahl Duschen im Jahr.
priceYesArbeitspreis in EUR/kWh.
waterYesWasser und Abwasser in EUR/m³.
factorYesNutzwärme je kWh eingesetzter Energie.
minutesYesMinuten je Dusche.
newflowYesAlternativdurchfluss in Litern pro Minute.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/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. The description adds that both scenarios share the same time and temperature and that water and heat costs are included, but says nothing about what the result contains (savings? payback? per year?) despite there being no output schema.

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 with the scope front-loaded and no filler. The German and English versions are near-duplicates, which is a small amount of redundancy but aids accessibility.

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

Completeness2/5

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

This is a ten-required-parameter calculator with no output schema and no explanation of the return value. With parameters like factor, cost, and price all mandatory, an agent needs to know what the tool produces (annual savings, payback period) to use it confidently, and the description does not say.

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 units and ranges on all ten parameters, so the baseline is 3. The description adds one genuine constraint beyond the schema — that minutes and temperature are held identical across the two flows — but does not clarify how cost, factor, and price combine.

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 verb (compare) and resource (two shower flow rates with water and energy costs), which is clearly distinct from measuring or minimum-flow siblings. It does not explicitly name a sibling it is not, 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 Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no prerequisites, and no pointer to alternatives such as sparbrause_mindestdurchfluss or duschdurchfluss_messen. The comparison framing implies a scenario, but an agent must infer it.

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