Skip to main content
Glama

getecoback-climate-weather

warmwasser_neustart_standzeit_ueberfluss

Read-only

Bei einem unterbrochenen Nutzungsvorgang zusätzlichen Anlauf vom ersten Anlauf trennen — Isolate restart run-up from the original draw.

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": {
      "erster_anlauf_l": "<erster_anlauf_l>",
      "wiederanlauf_l": "<wiederanlauf_l>",
      "geplant_zweck_l": "<geplant_zweck_l>",
      "pause_min": "<pause_min>"
    },
    "name": "warmwasser_neustart_standzeit_ueberfluss"
  }
}

Input Schema

NameRequiredDescriptionDefault
pause_minYesBeobachtete Zeit, in der die Entnahme geschlossen war.
wiederanlauf_lYesGemessene Menge bis zur Wiederkehr dieses Werts nach der Pause.
erster_anlauf_lYesGemessene Menge bis zum ersten Erreichen des Wunschwerts.
geplant_zweck_lYesBei diesem Wiederanlauf tatsächlich anderweitig sinnvoll genutzte Menge.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.7/5.0
Behavior2/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. Beyond that the description adds nothing: it does not say what is computed from the four measurements, whether the result is a volume or a ratio, or how the pause and planned-use inputs affect the outcome. For a calculation tool with no output schema, this leaves the agent guessing at the result.

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

Conciseness3/5

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

The description is short and front-loads the scenario, which is good. But the German sentence and its English translation are verbatim duplicates, so half the text is redundant rather than additive, and no space is used for the missing output information.

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?

With four required numeric inputs, no output schema, and a non-obvious computation, the description should explain what the tool returns and how the inputs relate. It instead only restates the scenario, leaving the agent unable to predict the result or verify a call was correct.

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 (erster_anlauf_l, wiederanlauf_l, geplant_zweck_l, pause_min) are already documented with units and bounds in the schema. The description adds no interpretation of how these values are combined or which one drives the separation logic, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific operation (separating the additional restart run-up from the first run-up) within a stated scenario (an interrupted draw). However, the resource is abstract and the description never says what the tool actually produces — a computed volume, a classification, or a corrected value. It does not differentiate itself from the many similarly named warmwasser siblings.

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 opening clause 'Bei einem unterbrochenen Nutzungsvorgang' gives an implicit trigger condition for when this tool applies. There is no explicit when-not guidance, no prerequisites, and no named alternative among the numerous warmwasser_* siblings that handle adjacent cases such as unplanned draw or waiting loss.

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