Skip to main content
Glama

getecoback-raumklima

saugroboter_d10_wischmodul_nachlauf

Read-only

Nächsten Schritt zwischen Wischen und Laden beim Dreame D10 Plus Gen 2 prüfen — Check the documented mop removal and care sequence for the D10 Plus Gen 2.

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>",
      "modul_montiert": "<modul_montiert>",
      "restwasser": "<restwasser>",
      "pad_gepflegt": "<pad_gepflegt>"
    },
    "name": "saugroboter_d10_wischmodul_nachlauf"
  }
}

Input Schema

NameRequiredDescriptionDefault
modellYesModell laut Typenschild.
restwasserYesRestwasser befindet sich im Wischmodul?
pad_gepflegtYesPad ist gemäß Anleitung gewaschen und trocken?
modul_montiertYesWischmodul noch eingesetzt?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.6/5.0
Behavior2/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 adds almost nothing beyond that: it does not say what happens when restwasser is true or pad_gepflegt is false, whether a failed check blocks charging, or what kind of result is returned. 'Documented sequence' hints at referencing an external procedure but is not elaborated.

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 and front-loads the model name, but it is essentially the same sentence stated twice in German and English, which is redundant rather than reinforcing. No wasteful paragraphs, but also no structure that helps an agent scan the trigger condition versus the action.

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 four-required-parameter, read-only check with no output schema, the description should convey how the booleans drive the outcome and what 'next step' means. The annotations and schema cover safety and inputs, but the decision logic and result shape remain unexplained, leaving a real gap for a sequencing/gating tool.

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%, so the four parameters (modell, modul_montiert, restwasser, pad_gepflegt) are fully self-documenting with enums and boolean meanings. The description mentions none of them and adds no semantics beyond the schema, so baseline 3 applies.

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 description names a concrete resource (mop module follow-up for the Dreame D10 Plus Gen 2) and a vague verb ('Nächsten Schritt ... prüfen'). It is clear this is a checklist/gate check around mop removal and care, but it never states what the tool actually produces, so an agent cannot tell precisely what 'prüfen' yields beyond a confirmation.

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?

No when-to-use or when-not guidance, and no alternative tool is named. Siblings such as saugroboter_teppich_wischmodus or saugroboter_sensorhinweis_pflege are plausibly adjacent, but the definition gives no routing hint; the agent must infer the trigger condition (between mopping and charging) from the phrase 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