Skip to main content
Glama

getecoback-climate-weather

induktion_ankochautomatik_fortkochstufe_zeitbeleg

Read-only

Vergleiche die beobachtete Dauer des Ankochstoßes mit der Handbuchzeile der bestätigten Fortkochstufe — Read Auto Heat-up duration against its exact continuation setting

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": {
      "modell_bestaetigt": "<modell_bestaetigt>",
      "fortkochstufe": "<fortkochstufe>",
      "modus_und_zwischenstufe_belegt": "<modus_und_zwischenstufe_belegt>",
      "beobachtetes_ende_s": "<beobachtetes_ende_s>",
      "messfenster_s": "<messfenster_s>",
      "kein_zeitgleicher_eingriff_bekannt": "<kein_zeitgleicher_eingriff_bekannt>"
    },
    "name": "induktion_ankochautomatik_fortkochstufe_zeitbeleg"
  }
}

Input Schema

NameRequiredDescriptionDefault
fortkochstufeYesFortkochstufe. Punkt kennzeichnet die belegte Zwischenstufe
messfenster_sYesEigene kombinierte Zeitmessunsicherheit, keine Herstellertoleranz
modell_bestaetigtYesGenau Miele KM 7464 FR (11022890) und die deutsche Modellzeile in Handbuch 11 163 871 bestätigt
beobachtetes_ende_sYesBeobachteter Statuswechsel nach Aktivierung auf derselben Zone, in Sekunden
modus_und_zwischenstufe_belegtYesAnkochautomatik und genaue Stufe dokumentiert, Zwischenstufen bei einem Punkt aktiviert
kein_zeitgleicher_eingriff_bekanntYesKeine manuelle Stufenänderung und keine beobachtete Stufen- oder Leistungsaufteilungsänderung in diesem Lauf

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 the safety profile is covered. The description adds that the comparison is against a manual row for the confirmed level, which is useful framing, but it says nothing about what happens on a mismatch or what the result looks like.

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 short sentences, comparison target front-loaded, no filler. The German/English duplication is mildly redundant but keeps the definition compact and readable.

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?

With six required parameters and no output schema, the definition leaves the result contract unspecified: an agent cannot tell whether it returns a pass/fail verdict, a delta, or a citation to the manual row. Preconditions are carried entirely by the schema descriptions, so the description is adequate but not complete for a verification tool.

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 six parameters are already documented in the schema, including the enum and the measurement-window uncertainty semantics. The description only gestures at two of them (duration, continuation level), so it adds no meaning beyond the schema – 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?

States a specific verb (compare/read) and a specific resource: the observed auto heat-up (Ankochstoß) duration against the manual row for the confirmed continuation level. It is clearly a verification tool rather than a general induction lookup, though it never names a sibling to distinguish itself from the many other induction evidence tools.

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 verb 'Vergleiche' implies this is a post-observation verification step, and the required parameters (confirmed model, documented mode, no simultaneous intervention) imply preconditions. But there is no explicit when-to-use/when-not guidance and no alternative named.

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