Skip to main content
Glama

getecoback-raumklima

induktion_topferkennung_auswahl_und_stufe_getrennt

Read-only

Lies ausgewählte Zone und eingestellte Leistungsstufe getrennt aus derselben Beobachtung — Distinguish automatic cookware selection from a recorded assigned 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>",
      "permanente_erkennung_aktiv": "<permanente_erkennung_aktiv>",
      "beobachtung": "<beobachtung>",
      "stufenbedienung_bestaetigt": "<stufenbedienung_bestaetigt>"
    },
    "name": "induktion_topferkennung_auswahl_und_stufe_getrennt"
  }
}

Input Schema

NameRequiredDescriptionDefault
beobachtungYesDokumentierter Ablauf auf derselben Zone
modell_bestaetigtYesGenau Miele KM 7464 FR (11022890) und die deutsche Modellzeile in Handbuch 11 163 871 bestätigt
permanente_erkennung_aktivYesEinstellung der permanenten Topferkennung zum Zeitpunkt bekannt
stufenbedienung_bestaetigtYesZur selben Kochzone ist eine tatsächlich ausgewählte Leistungsstufe protokolliert

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 safety and locality are covered. The description contributes the meaningful behavioral detail that both values are derived from one shared observation and reported separately, which shapes how results should be interpreted. It says nothing about what happens with 'unbekannt' or 'offen' inputs, or about the shape of the response, so it adds only moderate context beyond the annotations.

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?

Short and front-loaded: the German clause states the operation first, followed by a dash and the distinguishing nuance. The English half largely restates the German for a non-German reader, which is mild redundancy but not padding. No sentence is wasted on restating annotations or schema fields.

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 four-parameter, fully-specified read operation with no output schema, the description covers the core intent and the separation requirement. It does not indicate what the returned separated values look like, nor how it behaves in the ambiguous enum branches, which is a real gap given there is no output schema to explain return values. Adequate but not complete.

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%: all four required parameters carry explicit descriptions, and two have enumerations with meaningful members. The description adds no additional parameter-level meaning, such as how 'stufenbedienung_bestaetigt' interacts with 'beobachtung' when deriving the setting. Baseline 3 is appropriate when the schema does the explanatory work.

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 action (read out) on two specific facts (selected zone, set power level) plus the defining constraint that they come from the same observation and must be kept separate. The English half clarifies the exact distinction the tool draws between automatic cookware detection and a recorded assigned setting, which separates it from the many other induktion_* siblings. The long compound name is partly mirrored rather than transcended, but an agent can still tell what it does without opening the schema.

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 phrase 'getrennt aus derselben Beobachtung' implies the tool is for cases where two facts must not be conflated, which is implicit usage guidance. However, no sibling is named, no when-not condition is given, and there is no routing to alternatives such as the other cookware-detection or zone-assignment tools. The agent must infer the selection context from the description alone.

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