Skip to main content
Glama

getecoback-climate-weather

miele_wwr880_programm_waschmittelklasse_fussnote

Read-only

Für Express 20, Jeans, Wolle, Seide, Outdoor oder Gardinen die Waschmittelklasse und Fußnote des Miele-Handbuchs lesen — Decode the detergent types and physical forms recommended for named programmes.

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>",
      "programm": "<programm>"
    },
    "name": "miele_wwr880_programm_waschmittelklasse_fussnote"
  }
}

Input Schema

NameRequiredDescriptionDefault
programmYesGenau benanntes Programm auf dem WWR-880-WPS-Display.
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.6/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, covering the safety profile. The description adds useful context that the data comes from the Miele handbook and that it decodes detergent types and physical forms. It does not describe output format, lookup behavior, or limitations beyond the source, so it remains adequate rather than rich.

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 description is short and front-loads the applicable programmes before the decoded resource. The German and English phrasing is somewhat redundant, but it remains efficient and easy to parse.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple, read-only lookup with two fully described enum parameters and no output schema, the definition is nearly complete: it identifies the source manual and the decoded data. It does not explain the required modellbeleg parameter or the exact return shape, but those gaps are minor given the schema descriptions.

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 both parameters are fully documented in the schema, including the programme enum and the modellbeleg confirmation states. The description repeats the programme scope but adds no parameter-level detail beyond what the schema provides, making the baseline 3 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 action and resource: read/decode the detergent class (Waschmittelklasse) and footnote from the Miele manual for named programmes. It lists the relevant programmes (Express 20, Jeans, Wolle, Seide, Outdoor, Gardinen), making the purpose clear. It does not explicitly differentiate itself from sibling tools, so it stops short of a 5.

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?

The phrase 'Für Express 20, Jeans, Wolle, Seide, Outdoor oder Gardinen ... lesen' gives clear contextual guidance about when to use this tool. It implies it is for retrieving detergent class/footnote data for those programmes, but does not state when not to use it or name alternative 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