Skip to main content
Glama

getecoback-raumklima

roomba_absaugdock_app_taste_und_manueller_erfolg

Read-only

Trenne lokale Entleerungsfunktion von einem fehlenden App-Bedienelement beim zugeordneten Roomba — Distinguish the documented communication path when local evacuation works

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>",
      "autoempty_dock_bestaetigt": "<autoempty_dock_bestaetigt>",
      "lokale_entleerung_beobachtet": "<lokale_entleerung_beobachtet>",
      "app_taste": "<app_taste>"
    },
    "name": "roomba_absaugdock_app_taste_und_manueller_erfolg"
  }
}

Input Schema

NameRequiredDescriptionDefault
modellYesVollständiger Modellname am Gerät für die deutsche Ausführung
app_tasteYesSchaltfläche zum Leeren in der App bei angedocktem Gerät sichtbar
autoempty_dock_bestaetigtYesZugeordnete AutoEmpty- oder Clean-Base-Station und passender Absaugbehälter bestätigt
lokale_entleerung_beobachtetYesLokaler Vorgang wurde an dieser Station tatsächlich vollständig beobachtet

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.3/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 safety is covered; the description should then add what the call actually does with the four submitted observations. It adds nothing about how the local-evacuation result is separated from the app evidence, whether a verdict is returned, or what the agent learns afterwards.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

It is short, but the second half is a loose English restatement ('Distinguish the documented communication path when local evacuation works') that neither translates nor extends the German clause. Little waste in length, but the content is not front-loaded toward an actionable statement.

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 four-required-parameter diagnostic tool with no output schema, the description should convey what the collected evidence is used for and what the caller gets back. Neither is present, so an agent cannot judge the tool's outcome or how to act on it.

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 enums, so every parameter's meaning is already documented in structured form. The description adds no interpretation of what combinations of app_taste and lokale_entleerung_beobachtet mean, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description frames a topic ('Trenne lokale Entleerungsfunktion von einem fehlenden App-Bedienelement') rather than naming an action the tool performs or a result it produces. An agent cannot tell from this whether the tool records observations, returns a diagnosis, or compares data — only that it concerns a Roomba dock and a missing app button.

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?

No when-to-use guidance, no exclusions, and no pointer to alternatives, despite many sibling tools covering closely related Roomba dock topics (e.g. red-blinking, short-wait vacuum observation, container-role self-emptying). The agent must guess which of these diagnostic tools applies.

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