Skip to main content
Glama

getecoback-climate-weather

wasserkocher_zwei_aufguesse_servierplan

Read-only

Zwei vorgegebene Ziehzeiten mit einer gemeinsam benutzten Kanne rückwärts planen — Schedule two passive infusion timers with one kettle and a common serving time.

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": {
      "bis_servieren_min": "<bis_servieren_min>",
      "aufheizen_a_min": "<aufheizen_a_min>",
      "aufheizen_b_min": "<aufheizen_b_min>",
      "ziehen_a_min": "<ziehen_a_min>",
      "ziehen_b_min": "<ziehen_b_min>",
      "wechsel_min": "<wechsel_min>"
    },
    "name": "wasserkocher_zwei_aufguesse_servierplan"
  }
}

Input Schema

NameRequiredDescriptionDefault
wechsel_minYesEigene Zeit für Ausgießen und Neubefüllen zwischen den Durchgängen.
ziehen_a_minYesVorgegebene Ziehzeit von Aufguss A.
ziehen_b_minYesVorgegebene Ziehzeit von Aufguss B.
aufheizen_a_minYesEigene gemessene Heizdauer für Aufguss A.
aufheizen_b_minYesEigene gemessene Heizdauer für Aufguss B.
bis_servieren_minYesVerbleibende Minuten bis zum geplanten Servieren.

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?

The annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered, and the description adds genuinely useful domain context: the two timers are passive infusions that share a single kettle, so the drawback is that they depend on one another. It still doesn't say what the call returns, for example the ordered schedule or the derived start times, or what it does with infeasible inputs, such as a negative remaining time. That is reasonable but not rich.

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?

Two compact sentences that start with the scoping idea (backward planning) before naming the resource, with no filler, caveats, or restated name. The German and English versions duplicate each other, which is justified for a bilingual description but still adds length without adding information.

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?

The tool is a pure computation with six documented required numeric parameters and no output schema. The description covers the domain shape well, but it never says what the returned plan looks like, such as timestamps or offsets, nor which constraints make the plan infeasible. Since there is no output schema to fall back on, that leaves the completeness only adequate.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%: every one of the six parameters is documented in German, including wechsel_min (the time to pour out and refill). So the schema already carries the parameter semantics, and 3 is the expected baseline. The description goes slightly beyond that by explaining the domain model behind the six numbers: two separate Ziehzeiten, one shared Kanne, and a single gemeinsame Servierzeit. It thus clarifies why the parameters are grouped as they are.

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 concrete action and object pair: 'Schedule two passive infusion timers with one kettle and a common serving time', plus the 'rückwärts planen' (backward-plan) framing. That distinguishes it from the measurement, comparison, and fault-isolation siblings, but it never explicitly names a sibling or a boundary case.

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 description offers no statement about when to use this tool versus alternatives, no prerequisites, and no exclusions, even though several sibling tools also take 'zwei' quantities and time windows. A capable agent can infer that this is for two infusions that share a kettle, but the text itself gives no usage guidance.

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