Skip to main content
Glama

getecoback-raumklima

roomba_comboj9_stationstaste_sicherung_nachweis

Read-only

Ordne eine ohne Reaktion beobachtete Clean-Base-Taste beim Combo j9+ der tatsächlich dokumentierten Sperrfunktion zu — Check recorded dock-button lock evidence before diagnosing an unresponsive dock

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>",
      "genaue_nachfuellstation": "<genaue_nachfuellstation>",
      "funktionsstand_bestaetigt": "<funktionsstand_bestaetigt>",
      "sicherung_aktiv": "<sicherung_aktiv>",
      "lokale_reaktion": "<lokale_reaktion>"
    },
    "name": "roomba_comboj9_stationstaste_sicherung_nachweis"
  }
}

Input Schema

NameRequiredDescriptionDefault
modellYesVollständiger Modellname am Gerät für die deutsche Ausführung
lokale_reaktionYesDie Taste der Station zeigte in genau diesem Zeitraum eine Reaktion
sicherung_aktivYesKinder-/Haustiersicherung war laut Aufzeichnung in genau diesem Zeitraum aktiv
genaue_nachfuellstationYesBeobachtung an der automatischen Absaug- und Nachfüllstation des Combo j9+
funktionsstand_bestaetigtYesInstallierter Softwarestand mit der ab Version 23.37.12 dokumentierten Stationssperre bestätigt

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/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 the safety profile is covered; the description adds that the operation is evidence-based and recorded rather than a live probe, which is useful context. However, it does not say what the tool produces (no output schema exists, yet no return-value hint is given) or how 'offen'/'anderes_oder_offen' inputs are treated. No contradiction with the read-only annotation.

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 definition is short, but it is split into a German and an English sentence that partially restate each other rather than building a single front-loaded statement. The intended action (attribution) sits in the first half while the usage cue sits in the second, so an agent must read both halves to assemble the full picture.

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 five required parameters, a fully documented schema, and no output schema, the description does enough to frame the check but never indicates what the agent receives back — a verdict, a lock-function label, or a confirmation — nor what to do when the model field is 'anderes_oder_offen'. That is a meaningful gap for a tool whose entire product is an association result.

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 all five parameters, including three enums, are documented in the schema itself, so the schema carries the parameter burden. The description only implies the model- and time-window scoping ('in genau diesem Zeitraum') without adding parameter-level meaning beyond that. Baseline 3 is appropriate.

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 verb-and-resource pair: attributing an observed non-reactive Clean-Base button on the Combo j9+ to the actually documented lock function, based on recorded evidence. That is clearly distinct from the diagnostic siblings (red blinking, app button, suction start) even though no sibling is named. It is somewhat convoluted in phrasing, but an agent can tell what operation it performs.

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?

The English clause 'Check recorded dock-button lock evidence before diagnosing an unresponsive dock' gives a clear when-to-use condition and a sequencing constraint relative to diagnosis. It does not name any alternative tool or state when not to use this one, so it stops short of full 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