Skip to main content
Glama

getecoback-climate-weather

miele_wwr880_twindos_ultraphase_gegenfach_reset

Read-only

Nach Wechsel vom UltraPhase-Paar auf Colorwaschmittel oder ein anderes Mittel die Gegenseite im TwinDos-Menü prüfen — Review the opposite compartment after replacing the matched product pair.

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>",
      "paar_vorher": "<paar_vorher>",
      "aenderung": "<aenderung>"
    },
    "name": "miele_wwr880_twindos_ultraphase_gegenfach_reset"
  }
}

Input Schema

NameRequiredDescriptionDefault
aenderungYesTatsächlich beobachtete Änderung im TwinDos-Menü.
modellbelegYesSind WWR 880 WPS und die am eigenen Gerät einschlägige deutsche Anleitung M.-Nr. 11 767 692 bestätigt?
paar_vorherYesWar vor der beobachteten Änderung UltraPhase 1 und 2 als Paar eingerichtet?

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, matching the description's framing as a check/review rather than an actual mutation, which usefully offsets the misleading 'reset' in the name. The description does not explain what the check yields, how the three enum answers gate a result, or what happens on each outcome, so added behavioral context is limited.

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?

Short and front-loaded, but the German sentence is repeated almost verbatim in English, which is a redundant second clause rather than added information. The essential trigger is stated first, which is good; the duplication is the main waste.

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 narrow read-only verification step with three fully documented enum parameters and no output schema, the description covers the scenario adequately. It is thin on what the agent should do with each enum answer and how the three evidence parameters combine, leaving some inference to the caller.

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 parameters are fully described enums (modellbeleg, paar_vorher, aenderung), so the schema carries the semantic load. The description adds the scenario that makes 'aenderung' meaningful but gives no per-parameter detail, so the baseline of 3 applies.

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?

States a concrete action (die Gegenseite im TwinDos-Menü prüfen) tied to a specific trigger scenario (Wechsel vom UltraPhase-Paar auf Colorwaschmittel). It does not name or contrast any sibling tool, so it stops short of a 5, but an agent can tell what the tool is for.

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?

Supplies an explicit when-to-use condition: only after replacing the matched UltraPhase pair with Colorwaschmittel or another product. No when-not conditions or alternative tools are mentioned, so it is clear context rather than full routing guidance.

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