Skip to main content
Glama

getecoback-raumklima

induktion_km7464f_modus_wattangabe_zonenbezug

Read-only

Prüfe, zu welcher Zone und Leistungsstufe eine kopierte Wattangabe im Modellhandbuch gehört — Match a quoted watt figure to an exact zone and mode

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>",
      "kochzone": "<kochzone>",
      "modus": "<modus>",
      "angebot_watt": "<angebot_watt>"
    },
    "name": "induktion_km7464f_modus_wattangabe_zonenbezug"
  }
}

Input Schema

NameRequiredDescriptionDefault
modusYesModus, auf den sich die Angabe ausdrücklich bezieht
kochzoneYesZone anhand der Modellzeichnung; c+d gilt ausschließlich für verbundenen PowerFlex-Bereich
angebot_wattYesKopierter einzelner Leistungswert in Watt, keine Summe mehrerer Zonen
modell_bestaetigtYesGenau Miele KM 7464 FR (11022890) und die deutsche Modellzeile in Handbuch 11 163 871 bestätigt

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/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 the handbook-lookup framing, but says nothing about what happens if modell_bestaetigt is false, whether mismatched values are rejected, or in what form the zone/level answer is returned — gaps the annotations do not fill.

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?

One front-loaded clause states the task and its output concepts (zone, power level) immediately. The German and English halves are redundant, but that is a deliberate bilingual convention rather than filler; there is no wasted preamble.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only, four-parameter lookup with no output schema, the description conveys enough: the input is a copied watt figure, the lookup source is the model handbook, and the answer is a zone plus power level. It could still state the return shape explicitly, but nothing essential is missing for correct invocation.

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%, including enum meanings for modus and kochzone and the 1–15000 Watt bound on angebot_watt, so the schema carries the parameter burden. The description adds no syntax, format, or interpretation guidance beyond it; 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?

The description gives a specific verb ('Prüfe'/'Match') and a precise resource: a copied watt figure mapped to an exact zone and power level in the model handbook. That is concrete enough to select the tool without opening the schema, though it never names a sibling tool to contrast against (e.g. the related zonenauswahl or leistungsabgabe lookups).

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?

Usage is only implied: use it when you have a quoted watt value and need to know which zone/mode it belongs to. There is no explicit statement of when not to use it, no prerequisite ordering relative to the other induction tools, and no named alternative for adjacent questions such as vessel detection or booster runtime.

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