Skip to main content
Glama

getecoback-raumklima

miele_wwr880_baumwolle_vorwaeschzeit_stufen

Read-only

Die Vorwaschzeit bei Miele WWR 880 WPS Baumwolle mit Normal, +6, +9 oder +12 Minuten dem dokumentierten Phasenwert zuordnen — Read the timed cotton prewash phase without treating it as total cycle duration.

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>",
      "baumwolle": "<baumwolle>",
      "vorwaesche": "<vorwaesche>",
      "stufe": "<stufe>"
    },
    "name": "miele_wwr880_baumwolle_vorwaeschzeit_stufen"
  }
}

Input Schema

NameRequiredDescriptionDefault
stufeYesAbgelesene Einstellung zur Vorwaschzeit.
baumwolleYesIst das dort genannte normale Programm Baumwolle gewählt?
vorwaescheYesIst Vorwäsche im konkreten Lauf ausgewählt?
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

A3.5/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 the useful semantic constraint that the returned value is a phase value, not a total duration. It says nothing about how the four confirmation parameters gate the result (what happens on 'offen' or 'abweichend') or what the returned mapping looks like, and there is no output schema to fill that gap.

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 a single front-loaded sentence with no filler, but the em-dash stitching of a German clause onto an English imperative reads awkwardly and obscures whether the tool reads or assigns the value. The length is appropriate; the structure could be cleaner.

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 read-only lookup with no output schema, the essential purpose is conveyed, but the tool's actual behavior depends on four mandatory enum-gated confirmations whose combined effect (proceed vs. refuse on 'offen'/'abweichend') is never explained. An agent knows what the tool is about but not what happens when the evidence parameters are not confirmed.

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% with enums on all four parameters, so the schema already documents each field's meaning and allowed values. The description adds nothing about parameter interplay (e.g. that modellbeleg, baumwolle and vorwaesche must be confirmed before stufe is meaningful), so it holds at the baseline.

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 both the resource (Vorwaschzeit / timed prewash phase) and the specific model context (Miele WWR 880 WPS Baumwolle) plus the discrete values Normal/+6/+9/+12, which is far more specific than the bare tool name. It is understandable on its own, though the German/English mix makes the operative verb ('zuordnen' / 'read') slightly ambiguous as to whether the tool retrieves or records the value.

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

Usage Guidelines4/5

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

It gives a clear exclusion: the prewash phase must not be treated as total cycle duration, which steers the agent away from the most likely misuse. It does not name an alternative sibling tool for cycle-duration questions, but the negative condition supplies real selection context.

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