Skip to main content
Glama

getecoback-raumklima

waschmaschine_vorwaesche_bosch_miele_dosierweg

Read-only

Vorwäsche und Dosierweg bei Bosch WGB244A40 oder Miele WWR 880 WPS zusammen lesen — Check the documented main detergent route when prewash is selected.

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": {
      "geraet": "<geraet>",
      "modell_und_ausgabe_bestaetigt": "<modell_und_ausgabe_bestaetigt>",
      "vorwaesche": "<vorwaesche>",
      "dosierweg": "<dosierweg>"
    },
    "name": "waschmaschine_vorwaesche_bosch_miele_dosierweg"
  }
}

Input Schema

NameRequiredDescriptionDefault
geraetYesTatsächliches Gerät und genau zugeordnete deutsche Anleitung.
dosierwegYesFür die Hauptwäsche beabsichtigter und beobachteter Dosierweg.
vorwaescheYesIst Vorwäsche im konkreten Programm aktiviert?
modell_und_ausgabe_bestaetigtYesSind Modell, Ausführung und die genau angegebene deutsche Anleitung dem eigenen Gerät zugeordnet, bei Bosch einschließlich E-Nr.-Index?

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?

The readOnlyHint=true and openWorldHint=false annotations already establish that this is a safe, closed-world read. The description adds that the result concerns 'documented' main detergent route behavior, but it does not describe the return form, source excerpting, or how 'offen' values are handled beyond what the schema implies.

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 definition is short and front-loads the German purpose before the English gloss. The bilingual repetition is slightly redundant but useful for clarifying the specialized terms 'Vorwäsche' and 'Dosierweg'.

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 four-parameter, read-only documentation lookup with rich enum descriptions, the definition is adequate but still thin in one respect: there is no output schema, and the description does not say what kind of documented result the agent should expect. It covers the input condition well 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%, and all four required parameters have clear descriptions and enums, so the schema already carries parameter semantics. The description mentions the two model names but adds no further meaning about confirmation, prewash state, or dosing-route interpretation 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?

The description states a specific read action ('zusammen lesen' / 'Check') for a specific resource: the documented main detergent route when prewash is selected, for Bosch WGB244A40 or Miele WWR 880 WPS. It is clear enough to distinguish from unrelated Miele troubleshooting siblings, though it does not explicitly name an alternative tool.

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 usage condition: use this when prewash is selected and the main detergent route needs checking for the named Bosch or Miele models. It does not state when not to use it or name alternative tools, so it falls short of explicit 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