Skip to main content
Glama

getecoback-raumklima

bosch_wgb244a40_idos_pulver_manuell_kollision

Read-only

Beim Bosch WGB244A40 aktives i-DOS und zusätzlich geplantes manuelles Waschpulver für dieselbe Hauptwäsche erkennen — Detect duplicate main-detergent paths before starting.

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>",
      "i_dos_fluessig": "<i_dos_fluessig>",
      "manuelles_mittel": "<manuelles_mittel>"
    },
    "name": "bosch_wgb244a40_idos_pulver_manuell_kollision"
  }
}

Input Schema

NameRequiredDescriptionDefault
modellbelegYesStehen WGB244A40 und der E-Nr.-Index am eigenen Gerät und ist dafür die deutsche Anleitung 9001735129_F bestätigt?
i_dos_fluessigYesIst die automatische Flüssigwaschmitteldosierung für diesen Lauf laut Anzeige an, aus oder offen?
manuelles_mittelYesManuelles Vorhaben für diesen Lauf.

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, so the safety profile is covered. The description adds the temporal 'before starting' constraint and clarifies the duplicate-path scope, but does not describe how the detection result is surfaced.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with a compact English gloss after the dash. Every element — appliance, condition, action, and timing — earns its place with no wasted wording.

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 three-enum read-only check with no output schema, the description covers the scenario, timing, and purpose adequately. It could be strengthened by noting what a positive collision result means or which sibling to use for alternative checks.

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 have enum descriptions. The description mentions the two detergent paths conceptually but adds no extra meaning, syntax, or value guidance beyond the input 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 names the specific appliance (Bosch WGB244A40), the exact condition (active i-DOS plus planned manual powder for the same main wash), and the verb 'erkennen' / 'Detect'. This is a clear detection task, but it does not explicitly differentiate itself from sibling diagnostic 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?

The phrase 'before starting' establishes timing for the check, and the scenario implies when the tool applies. However, there is no explicit when-not guidance or routing to an alternative sibling tool.

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