Skip to main content
Glama

getecoback-raumklima

miele_wwr880_hauptwasch_cap_twindos_anzeige

Read-only

Bei gewählter Hauptwasch-Cap der Miele WWR 880 WPS die weiterhin sichtbare TwinDos-Anzeige erklären — Check the documented display exception when a main-wash cap disables TwinDos dosing.

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>",
      "cap_auswahl": "<cap_auswahl>",
      "twin_dos_anzeige": "<twin_dos_anzeige>"
    },
    "name": "miele_wwr880_hauptwasch_cap_twindos_anzeige"
  }
}

Input Schema

NameRequiredDescriptionDefault
cap_auswahlYesIn den Programmeinstellungen tatsächlich gewählte Cap-Funktion.
modellbelegYesSind WWR 880 WPS und die am eigenen Gerät einschlägige deutsche Anleitung M.-Nr. 11 767 692 bestätigt?
twin_dos_anzeigeYesIst die TwinDos-Anzeige im Display sichtbar aktiv, aus oder nicht ablesbar?

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 safety and locality are covered. The description adds a modest but real signal — that the answer comes from a documented display exception rather than a live device query — yet says nothing about the response content, source document handling, or failure cases.

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 scenario is front-loaded and the two sentences are short, but the German and English halves are near-verbatim restatements rather than complementary information, so roughly half the text is redundant. Nothing is wasted on filler beyond that duplication.

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?

Three required enum parameters, no output schema, and a read-only lookup: the definition covers the input situation adequately. What it omits is what the agent gets back — whether the tool explains why the display stays on, confirms it is expected behavior, or flags a mismatch — which matters because no output schema exists to fill that gap.

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 documented enums with inline descriptions (cap selection, model/document confirmation, display state), so the schema carries the semantic load. The description adds no interpretation of the enum values or of why modellbeleg matters beyond restating the scenario, making the 3 baseline correct.

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 specific verb ("erklären" / "Check") and a precise scenario: the TwinDos display that remains visible after a Hauptwasch-Cap is selected on the Miele WWR 880 WPS. That scenario is narrow enough to separate it from the TwinDos cartridge-counter and cap-residual-water siblings, though it never names an alternative outright.

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 condition "when a main-wash cap disables TwinDos dosing," which tells an agent the triggering situation. It gives no explicit when-not guidance and does not route to any sibling tool for the adjacent cap/TwinDos questions that dominate this catalog.

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