Skip to main content
Glama

getecoback-climate-weather

induktion_timer_akustisch_gegen_konkret_abgeschaltet

Read-only

Unterscheide den Küchenwecker von belegter Abschaltung der vorgesehenen Kochzone — Separate an audible timer event from zone shutoff

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>",
      "timeranzeige": "<timeranzeige>",
      "zielzone_zugeordnet": "<zielzone_zugeordnet>",
      "signal_gehoert": "<signal_gehoert>",
      "zone_nachher": "<zone_nachher>",
      "gleicher_zeitpunkt": "<gleicher_zeitpunkt>"
    },
    "name": "induktion_timer_akustisch_gegen_konkret_abgeschaltet"
  }
}

Input Schema

NameRequiredDescriptionDefault
timeranzeigeYesVorher tatsächlich dokumentierter Timer
zone_nachherYesStatus der betroffenen Zone unmittelbar nach dem Zeitpunkt
signal_gehoertYesEin Tonsignal wurde im betrachteten Zeitraum erfasst
modell_bestaetigtYesGenau Miele KM 7464 FR (11022890) und die deutsche Modellzeile in Handbuch 11 163 871 bestätigt
gleicher_zeitpunktYesTimerende und Zonenstatus Zeitstempel aus diesem selben Lauf
zielzone_zugeordnetYesEine Anzeige der Abschaltfunktion war eindeutig gerade dieser Zone zugeordnet

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/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 the safety profile is covered. Beyond that the description adds nothing: it does not say what verdict or evidence the tool produces (no output schema exists), nor what happens if 'modell_bestaetigt' or 'gleicher_zeitpunkt' is false, which for a six-required-parameter evidence tool is 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.

Conciseness4/5

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

A single front-loaded sentence that states the discrimination immediately. The only waste is the full bilingual duplication of the same content, which repeats rather than extends; the length itself is appropriate.

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?

For a six-required-parameter, no-output-schema classification tool, the description omits what the tool returns and how contradictory evidence inputs are handled. The rich schema compensates for parameter meaning, but the result of calling the tool remains entirely unexplained.

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 three enumerated fields, so the schema fully carries parameter meaning. The description mentions no parameter at all, leaving it at the baseline for high-coverage schemas.

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 specific discriminating task with a clear verb ('Unterscheide' / 'Separate') and two named objects: an audible kitchen-timer event versus a documented shutoff of the intended cooking zone. An agent can tell this is a classification/evidence tool rather than a control tool. It does not, however, differentiate itself from the many other induction-related siblings, so it stops short of a 5.

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?

There is no when-to-use condition, no prerequisites, and no named alternative such as the induction timer/abschaltzeit siblings. The discrimination framing loosely implies the ambiguous-timer scenario, but nothing tells the agent which sibling to prefer when it does not need to separate a tone from a zone shutoff.

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