Skip to main content
Glama

getecoback-climate-weather

miele_wwr880_cap_oder_pod_richtiger_eingabeweg

Read-only

Bei Miele WWR 880 WPS Waschmittel-Pods von ausgewiesenen Miele Caps für CapDosing unterscheiden — Identify the documented input path for a laundry pod or a Miele cap.

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>",
      "einheit": "<einheit>",
      "geplant": "<geplant>"
    },
    "name": "miele_wwr880_cap_oder_pod_richtiger_eingabeweg"
  }
}

Input Schema

NameRequiredDescriptionDefault
einheitYesPhysisch abgelesene Kennzeichnung auf der Packung.
geplantYesWo soll die identifizierte Einheit laut bisherigem Plan ankommen?
modellbelegYesSind WWR 880 WPS und die am eigenen Gerät einschlägige deutsche Anleitung M.-Nr. 11 767 692 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?

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safe, closed-world nature of the call is established. The description adds the CapDosing context but says nothing about what the result looks like or that the answer is a documentation-based classification rather than a device query.

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 core purpose front-loaded and no filler. The German/English duplication of the same sentence costs a little space without adding information.

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 narrow three-enum read-only classification tool the description is adequate to start, but with no output schema it should clarify what 'input path' means in the result and how the three required inputs drive the classification. It leaves the return semantics to inference.

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 described enums, so the schema carries the parameter burden. The description adds no meaning about how modellbeleg, einheit, or geplant interact, so the baseline 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 names a specific verb ('Identify' / 'unterscheiden') and resource ('the documented input path for a laundry pod or a Miele cap'), and frames the Miele WWR 880 WPS CapDosing distinction. It is clear what question the tool answers, though the bilingual duplication slightly muddies the single-sentence precision.

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 description signals that this applies when distinguishing pods from Miele caps for CapDosing, but it never states when to call this versus the many sibling tools about caps, Twindos, or dosage. No exclusions or preconditions are given.

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