Skip to main content
Glama

getecoback-raumklima

bosch_bfl524_reinigungsunterstuetzung_leichte_verschmutzung

Read-only

Die Reinigungsunterstützung für leichte Rückstände von starker Verschmutzung oder mechanischen Schäden abgrenzen — Determine the documented scope of Bosch cleaning assistance.

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": {
      "handbuch_belegt": "<handbuch_belegt>",
      "verschmutzung": "<verschmutzung>"
    },
    "name": "bosch_bfl524_reinigungsunterstuetzung_leichte_verschmutzung"
  }
}

Input Schema

NameRequiredDescriptionDefault
verschmutzungYesBeobachteter Befund.
handbuch_belegtYesGenaue deutsche Geräteausführung BFL524MS0 und Anwendbarkeit des Dokuments 9001610906_F am Gerät geklärt?

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 agent knows this is a safe, closed-corpus lookup and the description need not restate that. The description adds the substantive boundary logic (light residue vs. heavy soiling vs. mechanical damage), which is useful behavioral context. It does not say what the determination returns or how ambiguity is treated, so it goes beyond annotations only partially.

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?

A single front-loaded sentence that states the discriminating condition before the English gloss. The bilingual duplication is slightly redundant but the English half adds 'documented scope', which sharpens the intent. Nothing is wasted beyond that overlap.

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 two-parameter, fully described, closed-world classification with no output schema, the description gives enough to invoke it but not enough to anticipate results. It does not explain how an 'ungeklaert' observation is handled or how the handbook-applicability flag interacts with the soiling enum, which is the main open question for correct use.

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 coverage is 100%, so both parameters, including the enum labels 'leicht', 'stark', 'sichtschaden', 'ungeklaert', are already documented in structured form. The description echoes the light/heavy-soiling distinction and loosely maps 'mechanischen Schäden' onto 'sichtschaden', adding a little interpretive meaning. The 'ungeklaert' case and the handbook-applicability flag are not elaborated, so baseline 3 is right.

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 concrete operation — delimiting ('abgrenzen') cleaning assistance for light residue against heavy soiling or mechanical damage, i.e. establishing the documented scope of that assistance. The verb+resource pairing is specific enough to act on, and the framing (light residue vs. heavy soiling/damage) separates it conceptually from the sibling cleaner tools. It does not name any specific sibling as an alternative, which keeps it from a 5.

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 is only implied: an agent infers it should call this when it has a soiling observation and needs to know whether cleaning support is documented for it. There is no explicit when-to-use, when-not-to-use, or pointer to a related sibling such as the door-glass/control-panel cleaner tool. Adequate but leaves routing to inference.

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