Skip to main content
Glama

getecoback-raumklima

bosch_wgb244a40_idos_zwei_fluessigmittel_tankwahl

Read-only

Bei zwei i-DOS-Behältern mit Flüssigwaschmittel den für diesen Bosch-Lauf ausgewählten Tank identifizieren — Determine which of two configured detergent tanks 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": {
      "modellbeleg": "<modellbeleg>",
      "beide_tanks_fluessig": "<beide_tanks_fluessig>",
      "auswahl": "<auswahl>"
    },
    "name": "bosch_wgb244a40_idos_zwei_fluessigmittel_tankwahl"
  }
}

Input Schema

NameRequiredDescriptionDefault
auswahlYesFür den aktuellen Lauf eindeutig angezeigter Behälter.
modellbelegYesStehen WGB244A40 und der E-Nr.-Index am eigenen Gerät und ist dafür die deutsche Anleitung 9001735129_F bestätigt?
beide_tanks_fluessigYesIst die Gerätekonfiguration beider Behälter als Flüssigwaschmittel bestätigt?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/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 operational precondition (two liquid tanks, this run) but says nothing about what a lookup returns, how an 'offen' answer behaves, or whether any model-document verification gates the call beyond what the enum names state.

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?

One compact line with the constraint front-loaded (two liquid tanks), followed by the action. The German and English halves are near-duplicates, which wastes some space, though the bilingual phrasing plausibly mirrors the German source manual.

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 three-required-parameter, enum-driven, read-only lookup the definition is adequate, but with no output schema the description should say more about the result (e.g., whether 'offen' means undetermined selection). The model-reference gating parameter is never explained in prose.

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 documented enums, so the schema carries the parameter burden. The description reinforces that applicability depends on both tanks being liquid detergent, loosely tying to 'beide_tanks_fluessig', but adds no syntax, defaults, or interaction rules beyond that.

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 pairs a specific verb with a specific resource: identify which of two i-DOS liquid-detergent tanks was selected for this particular WGB244A40 run. The scoping (two containers, liquid detergent, this run) separates it from sibling tools about refilling, tank 2 rollback, or powder collisions without naming them explicitly.

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 context is implied by the precondition 'bei zwei i-DOS-Behältern mit Flüssigwaschmittel' — an agent can infer it applies only in the two-liquid-tank configuration. There is no explicit when-not guidance, no mention of what to do when the configuration is not confirmed, and no named alternative sibling for the one-tank case.

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