Skip to main content
Glama

getecoback-climate-weather

warmwasser_aufheizzeit_ideal

Read-only

Ideale Wiederaufheizdauer einer bekannten Wassermenge aus thermischer Leistung abschätzen — Estimate an ideal hot-water recovery time from delivered heat.

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": {
      "liter": "<liter>",
      "temperaturhub_k": "<temperaturhub_k>",
      "thermisch_kw": "<thermisch_kw>"
    },
    "name": "warmwasser_aufheizzeit_ideal"
  }
}

Input Schema

NameRequiredDescriptionDefault
literYesTatsächlich wieder erwärmte Wassermenge in Litern.
thermisch_kwYesBekannte mittlere thermische Leistung an das Wasser in kW.
temperaturhub_kYesBeobachteter Temperaturhub im Rechenszenario in Kelvin.

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?

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds real value with the word 'ideal' (and 'Rechenszenario' in the schema), signalling a theoretical best-case estimate rather than measured behavior, but it does not state the unit or form of the returned duration, which matters for a calculated result.

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 that names the computation and its inputs; nothing is padded. The German/English duplication roughly doubles the text length for no extra information, which keeps it just short of a 5.

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 read-only three-parameter calculator this is nearly adequate, and the parameters are exhaustively described in the schema. The notable remaining gap is the output, since there is no output schema and the description never says what unit the ideal recovery time is returned in.

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 coverage is 100%, so all three parameters (liter, temperaturhub_k, thermisch_kw) are fully documented in the schema with bounds and units. The description only references two of the three inputs in prose and adds no syntax or constraint detail beyond the schema, so the baseline 3 applies.

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 uses a specific verb ('abschätzen/estimate') and a specific resource ('ideale Wiederaufheizdauer' / hot-water recovery time) qualified by the inputs it derives from ('bekannten Wassermenge', 'thermischer Leistung'). It is clear what the tool computes, but it does not distinguish itself from near-siblings such as warmwasser_wartezeit_zapfstellen or warmwasser_warteverlust, which also deal with hot-water timing.

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 only implied: the phrasing 'aus thermischer Leistung' suggests this is the tool to reach for when water volume and heating power are known. There is no explicit when-to-use/when-not statement and no named alternative for cases like measured waiting times or losses, leaving the agent to infer the routing.

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