Skip to main content
Glama

getecoback-climate-weather

bosch_bfl524_drehteller_schleifen_aussenpruefung

Read-only

Schleifen des Mikrowellen-Drehtellers mit beobachteten Rückständen im Rollenringbereich abgleichen — Identify the documented user-observable cause of tray scraping.

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>",
      "schleifen_beobachtet": "<schleifen_beobachtet>",
      "aussenbefund": "<aussenbefund>"
    },
    "name": "bosch_bfl524_drehteller_schleifen_aussenpruefung"
  }
}

Input Schema

NameRequiredDescriptionDefault
aussenbefundYesSichtbarer, zugänglicher Bereich an Rollenring und Vertiefung bei ausgeschaltetem Gerät.
handbuch_belegtYesGenaue deutsche Geräteausführung BFL524MS0 und Anwendbarkeit des Dokuments 9001610906_F am Gerät geklärt?
schleifen_beobachtetYesEin Schleif- oder Kratzgeräusch ist tatsächlich beobachtet.

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 safety is covered. The description adds that the result is a 'documented user-observable cause', signalling the answer is grounded in manual documentation rather than open-world speculation — useful, but it says nothing about how inconclusive preconditions (handbuch_belegt=false, aussenbefund='nicht_geprueft') are handled or what the returned cause looks like.

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 with no filler, and the actionable German phrasing leads. The German/English duplication is slightly redundant but cheap insurance for a domain-specific term like 'Rollenringbereich'.

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 read-only diagnostic with full schema coverage, the essentials are present. The notable gap is the absence of an output schema combined with no description of the return value's shape — an agent cannot tell whether it receives a cause label, a citation to document 9001610906_F, or a pass/fail verdict.

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 three parameters, including the enum values, are already documented in the schema; that sets the baseline at 3. The description only restates the roller-ring residue condition already captured by 'aussenbefund' and adds no interpretation of how the booleans gate the diagnosis.

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 ('abgleichen' / 'Identify') with a specific resource (tray scraping caused by residues in the roller-ring area), so an agent can tell this is a diagnosis/matching tool rather than a lookup or repair action. It does not name any sibling to differentiate against, but the conjunction of 'Schleifen', 'Rückstände im Rollenringbereich' and 'documented cause' is narrow enough to be unambiguous.

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 'mit beobachteten Rückständen im Rollenringbereich' implies the triggering situation (residues actually observed in the roller-ring area), which is a usage precondition. However, there is no explicit when-not guidance (e.g. what to do when traces are absent or the manual applicability is unclarified) and no alternative tool is mentioned.

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