Skip to main content
Glama

getecoback-raumklima

roomba_aufladefehler21_aufnahme_und_ladeverlust

Read-only

Trenne dokumentierten Ladeverlust auf der Station von einer probeweise fehlenden Kontaktbestätigung — Compare a recorded on-dock charge loss with iRobot code 21

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": {
      "roomba_modell_belegt": "<roomba_modell_belegt>",
      "fehler_21": "<fehler_21>",
      "durchgehend_auf_dock": "<durchgehend_auf_dock>",
      "start_prozent": "<start_prozent>",
      "ende_prozent": "<ende_prozent>",
      "beide_ablesungen_belegt": "<beide_ablesungen_belegt>"
    },
    "name": "roomba_aufladefehler21_aufnahme_und_ladeverlust"
  }
}

Input Schema

NameRequiredDescriptionDefault
fehler_21YesWörtlicher Ladefehler 21 von diesem Vorgang gesichert
ende_prozentYesGemeldeter Akkustand am Ende
start_prozentYesGemeldeter Akkustand zu Beginn. Nur mit zwei bestätigten Ablesungen auswerten
durchgehend_auf_dockYesDer Roboter blieb zwischen beiden abgelesenen Akkuständen an derselben Station
roomba_modell_belegtYesRoomba-Modell und zugehörige Home Base oder Clean Base identifiziert
beide_ablesungen_belegtYesBeide Zahlen wurden in dieser Reihenfolge und am selben Gerät abgelesen

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.7/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, and the description is consistent with a non-mutating local comparison, so no contradiction. It adds the diagnostic intent — separating two interpretations of a charge loss — but with no output schema it never says what the result looks like or how the comparison resolves, leaving the most important behavioral question open.

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?

The statement is short and front-loaded with the discriminating action, but it is the same content stated twice in German and English with no additional information gained from the translation. Half the text is redundancy rather than value.

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 six-required-parameter diagnostic tool with no output schema, the description should at minimum indicate what the comparison yields and what 'offen' evidence does to the result. Neither is covered, and the preconditions that make the evaluation valid are only discoverable by reading individual schema fields.

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 coverage is 100% and every parameter carries a German description, including enum values and the 'nur mit zwei bestätigten Ablesungen' caveat, so the schema does the heavy lifting. The description only echoes the comparison framing (start/end percent, on-dock continuity, code 21 evidence) without adding format or edge-case semantics beyond it.

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

Purpose3/5

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

The verbs 'Trenne'/'Compare' plus the resources 'Ladeverlust auf der Station' and 'iRobot code 21' do convey a diagnostic discrimination between genuine on-dock charge loss and a merely tentative missing contact confirmation. However, the framing is abstract and never states what the tool actually produces — a verdict, a classification, or a comparison result — and nothing distinguishes it from the many similarly named Roomba diagnostic siblings.

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?

There is no statement of when to use this tool, when not to, or what alternative to pick. The only implied constraint ('nur mit zwei bestätigten Ablesungen auswerten') lives in a schema property description, not in the tool description, so the agent gets no routing guidance.

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