Skip to main content
Glama

getecoback-climate-weather

wasserkocher_entkalkung_zeitfenster

Read-only

Aus der Modellanleitung bekannte Pflegephasen bis zur nächsten Benutzung einplanen — Reserve an uninterrupted window for the kettle’s documented care steps.

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": {
      "vorgang_beschrieben": "<vorgang_beschrieben>",
      "vorbereitung_min": "<vorbereitung_min>",
      "einwirkzeit_min": "<einwirkzeit_min>",
      "spuelgaenge": "<spuelgaenge>",
      "je_spuelgang_min": "<je_spuelgang_min>",
      "verfuegbar_min": "<verfuegbar_min>"
    },
    "name": "wasserkocher_entkalkung_zeitfenster"
  }
}

Input Schema

NameRequiredDescriptionDefault
spuelgaengeYesAnzahl vorgeschriebener Spülgänge.
verfuegbar_minYesVerfügbare Zeit bis zum nächsten geplanten Gebrauch.
einwirkzeit_minYesDokumentierte Wartezeit für die vorgesehene Pflege.
je_spuelgang_minYesEigene Dauer je Spülgang.
vorbereitung_minYesEigene Dauer der Vorbereitung.
vorgang_beschriebenYesIst die gesamte Pflegefolge laut Anleitung für dieses Modell bekannt?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.5/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. Beyond that the description only says the phases come from the model manual and must be an uninterrupted window; it does not disclose what is produced (a schedule? a yes/no feasibility result?), what happens if the available time is too short, or how the 'vorgang_beschrieben' input affects behavior. With no output schema, this leaves a real gap.

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 action, which is good. However, it says the same thing twice in two languages ('Aus der Modellanleitung bekannte Pflegephasen' then 'documented care steps'), so half the text is redundant rather than additive.

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?

This is a six-required-parameter computation tool with no output schema and no annotation coverage of anything except read-only/closed-world. The description never explains what the computation produces or how the inputs combine, so an agent cannot predict the result shape or whether edge cases (insufficient available time, spuelgaenge=0) are handled.

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% and all six parameters carry their own German descriptions with ranges, so the schema does the heavy lifting. The description adds nothing parameter-specific beyond 'documented care steps', which justifies the baseline 3 rather than more.

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 conveys a scheduling action ('einplanen' / 'Reserve an uninterrupted window') around the kettle's documented care phases, so the general domain is discernible. But it never states the actual operation — whether it computes a schedule, checks whether the available time suffices, or returns a feasibility verdict — and it does not distinguish itself from the many sibling 'wasserkocher_*' 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?

The only contextual hint is 'bis zur nächsten Benutzung' (before the next planned use), which implies the tool applies when the care sequence must be fitted before reuse. There is no explicit when-to-use statement, no prerequisites, and no pointer to alternatives such as the other kettle-planning siblings.

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