Skip to main content
Glama

getecoback-raumklima

miele_wwr880_twindos_verschmutzung_und_spuelmenge

Read-only

Leicht, normal oder stark bei Miele TwinDos als gemeinsame Vorgabe für Dosierung und Spülwassermenge lesen — Identify the two process inputs affected by the selectable soil level.

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": {
      "modellbeleg": "<modellbeleg>",
      "auswahl_im_programm": "<auswahl_im_programm>",
      "beobachtete_stufe": "<beobachtete_stufe>"
    },
    "name": "miele_wwr880_twindos_verschmutzung_und_spuelmenge"
  }
}

Input Schema

NameRequiredDescriptionDefault
modellbelegYesSind WWR 880 WPS und die am eigenen Gerät einschlägige deutsche Anleitung M.-Nr. 11 767 692 bestätigt?
beobachtete_stufeYesAm Gerät lesbar gewählte Stufe.
auswahl_im_programmYesIst das Feld Verschmutzungsgrad bei diesem Programm tatsächlich wählbar?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/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 scope context by limiting the subject to exactly two process inputs rather than all program settings, but it says nothing about what a returned reading looks like, how the 'offen' (undetermined) states are reported, or what happens when modellbeleg is 'abweichend'.

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?

It is short and front-loads the soil levels, but the German clause and the English restatement partially duplicate each other ('gemeinsame Vorgabe für Dosierung und Spülwassermenge' / 'the two process inputs affected'). The em-dash construction is slightly awkward rather than a clean statement of purpose.

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 three-parameter read tool with no output schema, the description is adequate: it says the result is the identification of the two affected process inputs. It falls short on edge behavior, namely what the tool concludes when the model documentation check fails or the field is not selectable in the chosen program, which are clearly in scope given the parameters.

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 all three parameters are fully enumerated with their own descriptions, so the baseline is 3. The description restates the level values (leicht, normal, stark) which the schema already documents and adds no extra syntax, format, or interaction guidance for modellbeleg or auswahl_im_programm.

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 operation (read/identify) and a concrete subject: the three soil levels (leicht/normal/stark) as a joint specification for dosage and rinse-water quantity on Miele TwinDos. It is clear what is being looked up, though it never names a sibling, so an agent must infer the boundary against tools like wasser_plus_und_zusatzspuelgang on its own.

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: the agent can infer you call this when you need to know which two process inputs the selectable soil level drives. There is no explicit when-to-use, no when-not-to-use, and no named alternative tool despite many closely related siblings about TwinDos, Caps and water settings.

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