Skip to main content
Glama

getecoback-raumklima

miele_wwr880_singlewash_halbladung_dosiergrenze

Read-only

Miele WWR 880 WPS SingleWash unter 1 kg und die Empfehlung zur Hälfte des Halbladungswerts prüfen — Compute the documented small-load reference from the package half-load dose.

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>",
      "singlewash": "<singlewash>",
      "trocken_kg": "<trocken_kg>",
      "fluessig": "<fluessig>",
      "halbladung_ml": "<halbladung_ml>"
    },
    "name": "miele_wwr880_singlewash_halbladung_dosiergrenze"
  }
}

Input Schema

NameRequiredDescriptionDefault
fluessigYesIst das laut eigener Packung geeignete Mittel flüssig?
singlewashYesIst SingleWash im konkreten Programm tatsächlich aktiviert?
trocken_kgYesTrockene Beladung in kg. 0, falls noch nicht gewogen.
modellbelegYesSind WWR 880 WPS und die am eigenen Gerät einschlägige deutsche Anleitung M.-Nr. 11 767 692 bestätigt?
halbladung_mlYesPackungswert für eine halbe Ladung und die passenden Dosierbedingungen. 0, falls nicht belegt.

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 annotations already establish readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds little beyond that: it does not state how unresolved inputs (singlewash='offen', halbladung_ml=0, unsupported model) are handled, nor whether the computed reference is conservative or exact.

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?

A single compact sentence with the action and scope front-loaded. The German clause is effectively repeated in the English gloss, which is mild redundancy but the text stays short and earns its place.

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?

With five required parameters, no output schema and no annotations beyond read-only, the description should say what the computation returns (a millilitre figure? a ratio of the half-load dose?) and how it behaves under the 'offen' branches. It identifies the computation but leaves the result shape implicit.

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%, so the baseline is 3. The description does connect halbladung_ml to the dose and singlewash to the small-load threshold, but it adds no interpretation of the enum values or the 0-sentinel handling beyond what the schema already documents.

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 gives a specific verb ('Compute'/'prüfen') and a specific resource (the documented small-load reference derived from the package half-load dose for SingleWash under 1 kg). It is identifiable, but the bilingual split and the dense compound identifiers make it slower to parse than a single crisp statement.

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?

A usage condition is embedded ('SingleWash unter 1 kg'), but there is no explicit when-to-use / when-not-to-use statement and no reference to any alternative in the very large sibling set. The agent must infer from the parameter enums (e.g. 'offen' states) when this tool applies.

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