Skip to main content
Glama

getecoback-raumklima

roomba_absaugdock_rotes_blinken_und_neuversuche

Read-only

Ordne rotes Blinken oder wiederholte Evakuierungszyklen dem belegten AutoEmpty-Symptom zu — Interpret recorded AutoEmpty blockage signals without disassembly

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": "<modell>",
      "station_bestaetigt": "<station_bestaetigt>",
      "anzeige": "<anzeige>",
      "anzahl_zyklen": "<anzahl_zyklen>"
    },
    "name": "roomba_absaugdock_rotes_blinken_und_neuversuche"
  }
}

Input Schema

NameRequiredDescriptionDefault
modellYesVollständiger Modellname am Gerät für die deutsche Ausführung
anzeigeYesAnzeige vorn an der Station
anzahl_zyklenYesTatsächlich gehörte Evakuierungszyklen desselben Dockbesuchs; 0 nur wenn Beobachtung offen
station_bestaetigtYesKompatible automatische Absaugstation im Supportartikel eindeutig zugeordnet

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, matching the non-invasive 'interpret recorded signals' framing, so the safety profile is covered. The description contributes the useful note that no disassembly is required, but says nothing about how the assignment is reported, whether it can fail to match, or what the agent should do with a non-match.

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?

It is a single compact sentence with the German action first, then an English gloss. The bilingual restatement is mildly redundant but adds the 'no disassembly' detail rather than repeating the verb, so little is wasted.

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 four required parameters and no output schema, the description should indicate what the classification yields, and it only implies an assignment. All four inputs must be supplied, including confirmation that the dock is compatible, which is a precondition worth surfacing for an interpretive tool; the description leaves that implicit.

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% and both enum fields carry per-value descriptions, so the schema already does the heavy lifting on modell, anzeige, station_bestaetigt and anzahl_zyklen. The description adds no extra semantics such as how anzahl_zyklen interact with the retry signal, leaving this at the baseline.

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 German clause names a specific action and object: assign red blinking or repeated evacuation cycles to the documented AutoEmpty symptom ('Ordne ... dem belegten AutoEmpty-Symptom zu'). That is a classification task an agent can recognize, and the English gloss adds the constraint 'without disassembly'. It stops short of naming which sibling handles the contrasting cases (e.g. manual station-button success or container-role issues), so it is clear but not sibling-differentiated.

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 implied rather than stated: the tool applies when signals are already recorded and the goal is interpretation rather than repair. 'Without disassembly' sets a soft boundary against physical teardown tools, but there is no explicit when-not condition and no pointer to an alternative among the many roomba dock siblings.

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