Skip to main content
Glama

getecoback-raumklima

miele_wwr880_ultraphase_original_h1_h2_werkstabelle

Read-only

Die zwei UltraPhase-Startwerte in der WWR-880-WPS-Werkstabelle je Wasserhärte getrennt nachsehen — Read separate original UltraPhase setup references without inferring real consumption.

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>",
      "originalpaar": "<originalpaar>",
      "haerte": "<haerte>"
    },
    "name": "miele_wwr880_ultraphase_original_h1_h2_werkstabelle"
  }
}

Input Schema

NameRequiredDescriptionDefault
haerteYesDem Waschmaschinenanschluss zugeordneter Härtebereich.
modellbelegYesSind WWR 880 WPS und die am eigenen Gerät einschlägige deutsche Anleitung M.-Nr. 11 767 692 bestätigt?
originalpaarYesIst das originale UltraPhase-1/2-Paar im Geltungsbereich genau dieser Werksangabe 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 real value by stating the values are separated per hardness level and that no real consumption is inferred, but it says nothing about behavior for the 'offen' enum cases or about what happens when the confirmation fields are not 'bestaetigt'.

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 front-loaded sentence with the resource first and the scoping caveat second; no padding. The German/English mix is slightly awkward but does not cost clarity.

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?

No output schema exists, and the description does indicate the return shape conceptually: two UltraPhase start values per hardness from the factory table. Combined with full parameter documentation and read-only annotations, an agent has enough to call it correctly, though the confirmation-gated behavior is left unstated.

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 enums are self-documenting, so the schema carries the burden. The description only reinforces that results are split by Wasserhärte and that the original pair must match the scope; it adds no syntax or edge-case meaning beyond the schema.

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?

Names a specific verb (nachsehen/read) and a specific resource (die zwei UltraPhase-Startwerte in der WWR-880-WPS-Werkstabelle), plus the per-Wasserhärte split. An agent can tell this is a table lookup rather than a computation, though it doesn't explicitly contrast itself with the many 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 Guidelines3/5

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

Usage is implied by the phrase 'ohne reale Verbrauchswerte abzuleiten', which tells the agent this is a reference lookup and not a consumption estimator. However, it never states when to prefer this over a sibling or what preconditions must hold, so guidance stays implicit.

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