Skip to main content
Glama

getecoback-raumklima

roomba_j_volle_behaeltermeldung_nach_evakuierung

Read-only

Trenne bei Fehler 36 eine bestätigte Entleerung mit verbleibender Meldung von einer fehlgeschlagenen Entleerung — Correlate Roomba error 36 with the observed result of the same evacuation

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>",
      "fehler_36": "<fehler_36>",
      "absaugung_und_fuellzustand": "<absaugung_und_fuellzustand>",
      "meldung_nach_aussenpflege": "<meldung_nach_aussenpflege>"
    },
    "name": "roomba_j_volle_behaeltermeldung_nach_evakuierung"
  }
}

Input Schema

NameRequiredDescriptionDefault
modellYesVollständiger Modellname am Gerät für die deutsche Ausführung
fehler_36YesFehler 36 ausdrücklich für denselben Dockbesuch aufgezeichnet
meldung_nach_aussenpflegeYesDie Meldung kam nach freigegebener äußerer Pflege bei bestätigter Entleerung erneut
absaugung_und_fuellzustandYesDokumentation dieses Vorgangs

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 is covered; the description contributes the diagnostic logic of correlating error 36 with the observed evacuation result. However, with no output schema, it never states what the tool actually returns (a classification verdict, a label, a recommendation), which is the main behavioral gap.

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 definition is two short clauses with the discriminating condition ('bei Fehler 36') front-loaded. The German/English duplication is somewhat redundant but harmless and small.

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 read-only four-parameter diagnostic classification tool, the inputs and precondition are adequately covered. The absence of an output schema means the description should explain what the separation produces, and it does not, leaving the return value ambiguous.

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 enum-typed fields, so the schema fully documents each parameter. The description adds no syntax, ordering, or interpretation guidance beyond what the schema already says, which is the baseline case.

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 names a specific operation: separating a confirmed emptying with a lingering message from a failed emptying, scoped to error 36. The verb 'Trenne' (distinguish) plus the resource (error 36 evacuation outcome) is concrete enough to act on, though the phrasing is abstract and the bilingual restatement adds no extra precision.

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 via 'bei Fehler 36' and the required fehler_36 parameter, which signals the precondition for calling. There is no explicit when-not guidance and no named alternative among the many sibling Roomba diagnostics tools, so the agent must infer routing from the error code 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