Skip to main content
Glama

getecoback-raumklima

roomba_combo10max_absaugstart_kurze_wartebeobachtung

Read-only

Bewerte, ob eine kurze Beobachtung nach dem Andocken des Combo 10 Max die dokumentierte Verzögerung überhaupt abdeckt — Check observation coverage for the Combo 10 Max auto-empty delay

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>",
      "automatik_faellig": "<automatik_faellig>",
      "andocken_zeitpunkt_belegt": "<andocken_zeitpunkt_belegt>",
      "beobachtungsdauer_s": "<beobachtungsdauer_s>",
      "beginn_absaugung_belegt": "<beginn_absaugung_belegt>"
    },
    "name": "roomba_combo10max_absaugstart_kurze_wartebeobachtung"
  }
}

Input Schema

NameRequiredDescriptionDefault
modellYesVollständiger Modellname am Gerät für die deutsche Ausführung
automatik_faelligYesAbsaugung war für den konkreten Lauf laut Einrichtung fällig
beobachtungsdauer_sYesLückenlose beobachtete Sekunden ab bestätigtem Andocken
beginn_absaugung_belegtYesBeginn der Entleerung innerhalb dieser Beobachtung bestätigt
andocken_zeitpunkt_belegtYesEnde des Andockens eindeutig dokumentiert

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The readOnlyHint/openWorldHint annotations already cover the safety profile, so the description only needs to add semantics — it does state the tool renders a judgment about observation coverage rather than recording measurements. However, it says nothing about how the verdict is formed (e.g., what happens when automatik_faellig is 'nein' or a timestamp is unconfirmed) or what the response contains, which matters for a pure assessment tool.

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 German sentence with an English restatement is front-loaded with the verb and the object, but the bilingual duplication conveys no extra information and the hedging 'überhaupt' adds noise. It is short but partly redundant rather than dense.

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?

With five required parameters, no output schema, and a judgment-style result, the description should explain what the verdict consists of and how the inputs combine (e.g., that a coverage check requires a confirmed docking timestamp and continuous observation). It leaves the decision logic and return shape entirely unspecified, which is a substantial gap for this tool's complexity.

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 enums on three fields, so every parameter is already documented in the schema (model, due-ness, observed seconds, evacuation-start confirmed, docking timestamp documented). The description adds no per-parameter meaning such as the relevant delay threshold or how the 600 s maximum relates to it; 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 (bewerte/check) and a specific subject (whether a short post-docking observation covers the documented auto-empty delay for the Combo 10 Max), so an agent can tell this is a coverage-adequacy check rather than a data-fetch tool. It does not distinguish itself from any sibling, and no sibling performing a similar verdict for another model is named.

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 explicit when-to-use or when-not-to-use guidance and no named alternative. The usage is only inferable from the wording ('kurze Beobachtung ... abdeckt'), leaving the agent to guess whether this tool is for validating an existing observation or for deciding whether to keep observing.

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