Skip to main content
Glama

getecoback-raumklima

bosch_bfl524_reiniger_tuerscheibe_geraetefront_bedienfeld

Read-only

Glasreiniger für Türscheiben und Gerätevorderseite sowie Feuchtigkeit am Bedienfeld getrennt einordnen — Match the cleaning method to the exact front, pane or control surface.

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>",
      "flaeche": "<flaeche>",
      "mittel": "<mittel>"
    },
    "name": "bosch_bfl524_reiniger_tuerscheibe_geraetefront_bedienfeld"
  }
}

Input Schema

NameRequiredDescriptionDefault
mittelYesGeplantes Mittel.
flaecheYesZu reinigende Fläche.
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 safety profile is covered and the agent knows this is a closed-world advisory lookup. The description adds that the classification separates moisture at the control panel from glass cleaning, but it does not say what the result looks like or what happens when handbuch_belegt is false, which is the most consequential behavior for a read-only evaluator.

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 a single front-loaded sentence with no padding, and the surface constraint leads. The German/English duplication restates the same content twice, which is minor but not free.

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-parameter, fully documented, read-only classification tool with no output schema, the description covers purpose and surfaces adequately. It falls short on the gating parameter (manual applicability) and on what the tool returns or refuses, which is the main open question for an agent invoking it.

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 both enums carry their own descriptions, so the baseline is 3. The description names the surfaces and the cleaning agent, but adds no syntax or interpretation guidance beyond what the schema already states, notably nothing about the meaning of handbuch_belegt=false.

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 a concrete action (einordnen / match) and concrete resources (Türscheibe, Gerätevorderseite, Bedienfeld) so the agent understands this is a surface-to-cleaning-method classification tool. It does not explicitly distinguish itself from the adjacent cleaning-support sibling, but the pairing of surface plus cleaning agent makes the scope readable.

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?

"Match the cleaning method to the exact front, pane or control surface" implies the usage situation, but there is no explicit when-to-use or when-not-to-use statement and no referral to an alternative tool. The existence of a sibling about light soiling (reinigung_unterstuetzung_leichte_verschmutzung) makes an explicit boundary more valuable than the description provides.

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