Skip to main content
Glama

getecoback-climate-weather

wasserkocher_warmhalte_schlussabgleich

Read-only

Geplante Entnahmen mit einem dokumentierten Warmhaltefenster nach dem Aufheizen abgleichen — Check serving times against the kettle’s documented holding interval.

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": {
      "modus_bestaetigt": "<modus_bestaetigt>",
      "dauer_min": "<dauer_min>",
      "erste_entnahme_min": "<erste_entnahme_min>",
      "spaeteste_entnahme_min": "<spaeteste_entnahme_min>"
    },
    "name": "wasserkocher_warmhalte_schlussabgleich"
  }
}

Input Schema

NameRequiredDescriptionDefault
dauer_minYesDokumentierte Zeit bis zum Ende des Warmhaltemodus.
modus_bestaetigtYesAnleitung bestätigt den Warmhaltemodus in der gewählten Einstellung.
erste_entnahme_minYesMinuten zwischen abgeschlossenem Aufheizen und der ersten Entnahme.
spaeteste_entnahme_minYesMinuten zwischen abgeschlossenem Aufheizen und der letzten Entnahme.

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 the holding window is 'dokumentiert' (documented) and that comparison happens after heating, but it does not say what the tool returns on a mismatch or that it validates any documented instruction. With annotations carrying the safety burden, this is adequate but thin.

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?

Short and front-loaded, but the German sentence and the English sentence say the same thing, making roughly half the text redundant. The core action is stated in the first clause, which is good, yet the duplication costs efficiency.

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 read-only validation tool with four fully documented required parameters and no output schema, the definition is minimally sufficient. However, with no output schema present, the description should indicate what a successful vs. failing reconciliation yields, and it does not.

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 all four parameters self-documented, so the baseline is 3. The description's mention of 'nach dem Aufheizen' loosely frames the minute offsets but adds no constraint, unit, or edge-case 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?

States a concrete verb+resource pair: reconcile planned withdrawals ('Geplante Entnahmen') against a documented holding interval after heating. An agent can infer it is a comparison/validation tool. It does not name or distinguish itself from near-identical siblings such as wasserkocher_wahlstufe_abgleichen, so sibling differentiation is absent.

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?

No explicit when-to-use, when-not-to-use, or alternative tool is given. Usage must be inferred from the phrase 'Geplante Entnahmen' (planning serving times). Nothing tells the agent what to do when the check fails or which sibling handles related settings checks.

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