Skip to main content
Glama

getecoback-raumklima

duschfolge_warmwasservorrat_einordnen

Read-only

Aus gemessenem Mischwasservolumen abschätzen, wie viele gleich lange Duschen ohne Nachheizen hineinpassen — Estimate consecutive showers using a known usable mixed-water volume.

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": {
      "nutzbares_mischwasser_l": "<nutzbares_mischwasser_l>",
      "durchfluss_l_min": "<durchfluss_l_min>",
      "minuten_je_dusche": "<minuten_je_dusche>"
    },
    "name": "duschfolge_warmwasservorrat_einordnen"
  }
}

Input Schema

NameRequiredDescriptionDefault
durchfluss_l_minYesGemessener Duschdurchfluss in Litern pro Minute.
minuten_je_duscheYesMinuten mit laufendem Wasser je Dusche.
nutzbares_mischwasser_lYesNutzbares Mischwasservolumen aus dokumentierter Prüfung bei vergleichbarer Temperatur, in Litern. Kein bloßes Tankvolumen.

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 safety is covered. The description adds real behavioral context by disclosing the model assumptions ('ohne Nachheizen', 'gleich lange Duschen'), but says nothing about the result's form (count vs. fractional), rounding, or the fact that it is a pure computation with no side effects.

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?

A single front-loaded sentence with the core condition stated first. The German and English halves are fully redundant, which costs a little space but does aid bilingual disambiguation at negligible length.

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 three-parameter, read-only calculation with complete schema documentation and no output schema, the description is nearly sufficient. The only material omission is what the returned value looks like (integer shower count vs. fractional estimate), which matters for interpreting the result.

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%, so all three parameters are already fully documented, including the important caveat 'Kein bloßes Tankvolumen'. The description only restates that the volume is measured/known and adds no new syntax, unit, or constraint meaning beyond the schema.

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 (abschätzen / estimate) and a concrete resource (how many equal-length consecutive showers fit into a measured mixed-water volume without reheating). It is clearly a calculation tool, distinguishable from measurement siblings such as duschdurchfluss_messen, though it never names an alternative explicitly.

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: 'aus gemessenem Mischwasservolumen' signals that a usable volume must already have been determined elsewhere before calling this. There is no explicit when-to-use/when-not statement and no pointer to the sibling that produces that input value.

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