Skip to main content
Glama

getecoback-raumklima

bosch_wgb244a40_idos_behaelter2_rolle_ruecksetzung

Read-only

Nach Umstellung von Bosch i-DOS Behälter 2 zwischen Weichspüler und Flüssigwaschmittel die zurückgesetzte Basis prüfen — Verify the base setting after changing the tank role.

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>",
      "bisher": "<bisher>",
      "jetzt": "<jetzt>",
      "neue_basis_belegt": "<neue_basis_belegt>"
    },
    "name": "bosch_wgb244a40_idos_behaelter2_rolle_ruecksetzung"
  }
}

Input Schema

NameRequiredDescriptionDefault
jetztYesNachweisbar neu eingestellte Rolle von Behälter 2.
bisherYesBisher eindeutig belegte Rolle von Behälter 2.
modellbelegYesStehen WGB244A40 und der E-Nr.-Index am eigenen Gerät und ist dafür die deutsche Anleitung 9001735129_F bestätigt?
neue_basis_belegtYesWurde nach dem Wechsel eine passende neue Basis für Produkt und örtliche Härte dokumentiert?

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?

The readOnlyHint=true annotation already establishes that this is a safe verification operation, and the description is consistent with that by describing a check rather than a mutation. It adds the useful context that the check happens after a role change, but it does not explain what the verification returns or how a failed check would appear.

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 description is short, front-loads the verification purpose, and contains no filler beyond the German/English bilingual restatement. That duplication is mildly redundant but does not obscure the meaning.

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 verification tool with no output schema, the description gives enough context to understand the scenario but not enough to interpret the result. It would benefit from stating what 'Basis prüfen' confirms or returns.

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%, so all four parameters and their enum meanings are already documented in the schema. The description supplies the overall scenario but does not add parameter-level detail beyond what the schema provides, making the baseline score appropriate.

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 verb and resource: verify the reset base setting after changing the role of Bosch i-DOS tank 2 between fabric softener and liquid detergent. It is clearly more specific than the name alone, but it does not explicitly distinguish itself from sibling tools such as the tank-selection or refill checks.

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 'Nach Umstellung ... prüfen' gives an implied trigger condition: use this after a tank-role change. However, it does not say when not to use it or name any alternative check for related i-DOS scenarios.

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