Skip to main content
Glama

getecoback-raumklima

miele_beutelsignal_feinstaub_fusseln_abgleichen

Read-only

Ordne eine Abweichung zwischen Beutelanzeige und sichtbar erfasster Füllung nach der zuletzt beobachteten Staubart ein — Reconcile early or delayed bag-full signals with the recorded material

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": {
      "beutelsauger_bestaetigt": "<beutelsauger_bestaetigt>",
      "signal": "<signal>",
      "sichtzustand": "<sichtzustand>",
      "sauggut": "<sauggut>"
    },
    "name": "miele_beutelsignal_feinstaub_fusseln_abgleichen"
  }
}

Input Schema

NameRequiredDescriptionDefault
signalYesVor einer Kontrolle abgelesene Geräteanzeige
sauggutYesWas in der vorliegenden Aufzeichnung überwog
sichtzustandYesDirekt dokumentierter Zustand am ausgeschalteten Gerät
beutelsauger_bestaetigtYesMiele Beutelmodell mit dokumentierter Wechselanzeige bestätigt

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?

The annotations already declare readOnlyHint=true and openWorldHint=false, so the agent knows this is a closed-world, non-mutating operation; the description adds the framing that the result is an interpretive classification ('einordnen') rather than a measurement. It does not say what the reconciliation result looks like, whether confidence or ambiguity is reported, or how conflicting inputs are resolved.

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?

Two short sentences with the discrepancy condition front-loaded. The bilingual restatement is somewhat duplicative, but the English half does contribute new detail ('early or delayed bag-full signals') that the German half omits, so little is wasted.

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 classification tool with no output schema, the definition covers what it does and when, but never indicates what the classification result contains or how a 'no discrepancy' case is reported. Adequate but with a clear gap on the return side.

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 three explanatory enums, so the parameters are already well documented. The description loosely maps to them (Beutelanzeige→signal, sichtbare Füllung→sichtzustand, Staubart→sauggut) but adds no enum semantics or interaction rules beyond the schema, so the baseline of 3 applies.

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 verb ('Ordne ... ein' / reconcile, classify) and a specific resource: a discrepancy between the bag-full indicator and the visually recorded fill level, attributed to the last observed dust type. That is enough to distinguish it from the surrounding 'abgleichen' siblings, though it does not name any of them explicitly.

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 only implied by the precondition 'Abweichung zwischen Beutelanzeige und sichtbar erfasster Füllung' — you use it when the two disagree. There is no explicit when-not guidance, no mention of prerequisites (e.g. a confirmed bag model, which one parameter does encode), and no routing to alternative tools for related Miele bag questions.

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