Skip to main content
Glama

getecoback-raumklima

roomba_combo_j5_behaelterrolle_selbstentleerung

Read-only

Prüfe bei fehlender Selbstentleerung, ob im genau genannten Roomba der dafür vorgesehene Behälter eingesetzt war — Account for the documented bin-dependent self-empty function

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>",
      "behaelter": "<behaelter>",
      "clean_base_bestaetigt": "<clean_base_bestaetigt>",
      "keine_selbstentleerung_beobachtet": "<keine_selbstentleerung_beobachtet>"
    },
    "name": "roomba_combo_j5_behaelterrolle_selbstentleerung"
  }
}

Input Schema

NameRequiredDescriptionDefault
modellYesVollständiger Modellname am Gerät für die deutsche Ausführung
behaelterYesAm Roboter für diesen Lauf sicher zugeordneter Behälter
clean_base_bestaetigtYesZugehörige Clean Base für dieses Gerät und denselben Lauf dokumentiert
keine_selbstentleerung_beobachtetYesAusbleiben der Selbstentleerung wurde direkt beobachtet

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/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 agent knows this is a safe, closed-domain check. The description adds domain context: the self-empty function is documented as bin-dependent. However, it does not explain what the tool returns, how the boolean inputs interact with the check, or what a positive/negative result means.

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 a single, front-loaded sentence that puts the triggering condition first. The English clause after the dash adds rationale but is somewhat redundant with the German statement. There is no unnecessary bulk.

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 diagnostic with four required parameters and no output schema, the description explains when to check and what to check. It omits how the result is returned or how the agent should interpret the boolean inputs, which is a meaningful gap given the absence of an output schema.

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 enum descriptions for model and bin plus explanations for both booleans. The description references the model and the bin but adds no additional syntax, interpretation, or edge-case meaning beyond what the schema provides. The baseline of 3 is appropriate when the schema fully documents parameters.

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 states a specific diagnostic action: verify whether the designated bin was installed in the named Roomba when self-emptying is missing. It identifies the resource (Behälter) and the failure condition (fehlende Selbstentleerung), making the tool distinguishable from generic Roomba troubleshooting siblings. It does not explicitly name a sibling alternative, but the purpose itself is clear.

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?

It gives an explicit trigger: use this when self-emptying is absent. That is a clear usage context, but there are no exclusions or pointers to alternative sibling tools for related Roomba diagnostics. The guidance is sufficient for when to use it, though not for when not to.

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