Skip to main content
Glama

getecoback-raumklima

miele_guard_l1_tu_halteplatte_sperrklinke

Read-only

Prüfe vor einem weiteren Beutelkauf, welche sichtbare Einrastbedingung am ausgeschalteten HS22 offen ist — Locate the missing TU seating proof before replacing a bag

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": {
      "hs22_bestaetigt": "<hs22_bestaetigt>",
      "tu_typ_belegt": "<tu_typ_belegt>",
      "halteplatte_beide_seiten": "<halteplatte_beide_seiten>",
      "sperrklinke_eingerastet": "<sperrklinke_eingerastet>",
      "deckel_blockiert": "<deckel_blockiert>"
    },
    "name": "miele_guard_l1_tu_halteplatte_sperrklinke"
  }
}

Input Schema

NameRequiredDescriptionDefault
tu_typ_belegtYesTU-Typ auf passender Packung eindeutig zugeordnet
hs22_bestaetigtYesDeutsche Guard L1 Ausführung mit Typ HS22 und zugeordneter Anleitung M.-Nr. 13 114 040 bestätigt
deckel_blockiertYesBedienbarer Staubraumdeckel wurde bei normaler Handhabung als blockiert beobachtet
sperrklinke_eingerastetYesTürkise Sperrklinke schließt mit eindeutiger Einrast-Bestätigung
halteplatte_beide_seitenYesPlatte in beiden Führungen bis zum Anschlag sichtbar erfasst

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The annotations already establish readOnlyHint=true and openWorldHint=false, and the description is consistent with that. Beyond the annotations, it adds the 'ausgeschalteten HS22' precondition and the notion of checking visible seating proof, but it does not explain the response format, interpretation of 'offen', or any error/edge-case behavior.

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?

The description is one front-loaded sentence with a short English gloss, and the action and precondition appear early. The bilingual repetition is slightly redundant but not bloated, and every clause contributes context.

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 five-parameter read-only diagnostic with rich schema coverage, the description supplies the usage context and device state but does not explain what the tool returns or how an agent should interpret the result. Since there is no output schema, that missing return-value context leaves a meaningful gap.

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 all five required parameters documented and four using enums. The description adds contextual framing such as 'TU seating proof' and 'sichtbare Einrastbedingung', but it does not add parameter-level meaning beyond what the schema already provides.

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 uses a specific verb, 'Prüfe', and a specific resource, 'sichtbare Einrastbedingung am ausgeschalteten HS22', plus a pre-bag-purchase context. It is clear enough to distinguish a diagnostic seating check from a replacement action, but it does not name any sibling alternative or fully disambiguate from related Miele guard checks.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly states when to use the tool: before another bag purchase and before replacing a bag, and it specifies the HS22 must be switched off. It does not give when-not-to-use conditions or point to alternative sibling tools, which keeps it below 5.

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