Skip to main content
Glama

getecoback-raumklima

dreame_d10_absaugung_nicht_stoeren_verlauf

Read-only

Vergleiche einen ausgelassenen D10-Absaugvorgang mit der wirklich aktiven Nicht-stören-Einstellung — Check whether recorded D10 auto-empty suppression matches the applicable DND state

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_bestaetigt": "<modell_bestaetigt>",
      "rueckkehr_bestaetigt": "<rueckkehr_bestaetigt>",
      "absaugung": "<absaugung>",
      "nicht_stoeren": "<nicht_stoeren>",
      "absaugung_konfiguriert": "<absaugung_konfiguriert>"
    },
    "name": "dreame_d10_absaugung_nicht_stoeren_verlauf"
  }
}

Input Schema

NameRequiredDescriptionDefault
absaugungYesAutomatische Entleerung bei dieser Rückkehr vollständig beobachtet
nicht_stoerenYesNicht stören war zum Zeitpunkt der Rückkehr in der App aktiv
modell_bestaetigtYesDreame D10 Plus Gen 2 mit zugehöriger Absaugstation auf dem Typenschild oder in den Unterlagen zum beobachteten Gerät bestätigt
rueckkehr_bestaetigtYesRückkehr zur Basis nach der Reinigung wurde beobachtet
absaugung_konfiguriertYesAutomatische Entleerung wäre für diese Rückkehr ohne Nicht-stören-Einstellung fällig gewesen

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/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 comparison is between a recorded omission and the effective DND configuration, which is useful behavioral framing. However, with no output schema it says nothing about what the comparison produces (match/mismatch/indeterminate, and how the 'offen' values are handled), which is the key behavioral question for a check tool.

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?

A single front-loaded sentence with the German statement followed by a compact English gloss; the verb and subject come first and there is no padding. The bilingual duplication is mildly redundant but serves comprehension rather than wasting space.

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 and no output schema, the description covers what is compared but not what the agent gets back or how to interpret an 'offen' input, which is the natural follow-up question after invoking it. It is sufficient to decide to call the tool, but not to fully reason about its 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 description coverage is 100% and the enum/boolean fields are already documented precisely in the schema, so the description need not restate them. It adds no extra parameter meaning (e.g. how 'offen' should be used, or that all five confirmations must be supplied). Baseline 3 applies when the schema does the heavy lifting.

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 concrete verb ("Vergleiche") and two concrete resources: a recorded/omitted D10 auto-empty event and the actually active DND setting. An agent can immediately tell this is a consistency-check tool rather than a plain log/diary tool like the sibling 'verlauf' entries. It stops short of naming how it differs from adjacent D10/station tools, so it is clear but not sibling-differentiating.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the framing: use it when you have a recorded auto-empty suppression and want to verify it against the applicable DND state. There is no explicit when-not-to-use, no mention of prerequisites (e.g. that model and return must be confirmed first), and no routing to alternative tools. Adequate but leaves the trigger conditions to inference.

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