Skip to main content
Glama

getecoback-raumklima

dusche_waermeleistungsbedarf

Read-only

Kontinuierliche Wärmeleistung beim Duschen aus Durchfluss und Temperaturhub abschätzen — Estimate the continuous thermal output needed at a given shower flow.

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": {
      "durchfluss_l_min": "<durchfluss_l_min>",
      "kalt_c": "<kalt_c>",
      "misch_c": "<misch_c>",
      "nutzwaerme_kw": "<nutzwaerme_kw>"
    },
    "name": "dusche_waermeleistungsbedarf"
  }
}

Input Schema

NameRequiredDescriptionDefault
kalt_cYesGemessene Kaltwassertemperatur in Grad Celsius.
misch_cYesGemessene Mischwassertemperatur in Grad Celsius.
nutzwaerme_kwYesDokumentierte, an das Wasser übertragene Leistungsgrenze in kW beim betrachteten Betriebspunkt.
durchfluss_l_minYesDurchfluss bei gewählter Einstellung in Litern pro Minute.

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 readOnlyHint=true and openWorldHint=false, so the agent knows this is a safe, bounded calculation. The description adds that this is an estimate rather than a direct measurement, but it does not disclose assumptions, calculation behavior, or what the returned thermal-output value represents in detail.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The definition is a single, front-loaded sentence that states the core computation without filler. The bilingual phrasing is slightly redundant but does not meaningfully reduce clarity or conciseness.

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?

For a simple four-parameter calculation with no output schema, the description identifies the tool's purpose and the main input dimensions. However, it does not explain the return value more precisely, state units for the result, or mention the role of nutzwaerme_kw, leaving some completeness gaps.

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 four parameters are fully documented in the schema. The description mentions flow and temperature lift but does not add meaning beyond the schema for nutzwaerme_kw or the other parameters; baseline 3 is appropriate when the schema carries parameter semantics.

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) and resource (kontinuierliche Wärmeleistung beim Duschen), with the inputs (Durchfluss und Temperaturhub) also stated. It is clear what the tool computes, though it does not explicitly distinguish itself from nearby shower-related tools.

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 explicit guidance on when to use this tool versus alternatives such as duschdurchfluss_messen or duschwasser_mischverhaeltnis. The context of use is implied by 'beim Duschen', but no when/when-not conditions or alternative routing are provided.

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