Skip to main content
Glama

getecoback-raumklima

miele_wwr880_caps_anzahl_und_vorwaeschefunktion

Read-only

CapDosing der Miele WWR 880 WPS auf eine Cap je Lauf und die Funktion der ausgewählten Cap prüfen — Check that cap count and purpose fit one wash programme.

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>",
      "geplante_caps": "<geplante_caps>",
      "cap_funktion": "<cap_funktion>",
      "waschmittel_cap_fuer_vorwaesche": "<waschmittel_cap_fuer_vorwaesche>"
    },
    "name": "miele_wwr880_caps_anzahl_und_vorwaeschefunktion"
  }
}

Input Schema

NameRequiredDescriptionDefault
modellbelegYesSind WWR 880 WPS und die am eigenen Gerät einschlägige deutsche Anleitung M.-Nr. 11 767 692 bestätigt?
cap_funktionYesEindeutig abgelesene Funktion der einzelnen geplanten Cap.
geplante_capsYesGeplante Caps in diesem einen Lauf, ganze Stückzahl.
waschmittel_cap_fuer_vorwaescheYesSoll diese Waschmittel-Cap laut Plan die Vorwäsche abdecken?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The readOnlyHint=true and openWorldHint=false annotations already establish that this is a safe, closed-world check. The description reinforces the validation purpose but does not disclose what the check returns, how mismatches are surfaced, or other behavioral details beyond the annotations.

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?

The definition is compact and front-loads the specific Miele model and CapDosing context. The German sentence and English gloss repeat the same content, which is slightly redundant but still efficient and free of filler.

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-parameter, fully required validation tool with rich schema descriptions and read-only annotations, the description gives enough context to understand the purpose. However, with no output schema, it does not explain what the validation result looks like or how a failed check is reported.

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 coverage is 100%, so the schema already documents all four parameters. The description adds a little meaning by mentioning one cap per run and the selected cap's function, but it does not mention the model-evidence or pre-wash-cap parameters. Baseline 3 is appropriate.

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 verification task for the Miele WWR 880 WPS CapDosing system: checking one cap per run and the function of the selected cap. It is clearly about validation rather than configuration, but it does not explicitly distinguish itself from the many similar WWR 880 sibling tools.

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

Usage Guidelines2/5

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

The description implies the tool is used to check cap count and purpose against a wash programme, but it gives no explicit when-to-use guidance, prerequisites, or alternatives among the numerous sibling cap and dosing tools.

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