Skip to main content
Glama

getecoback-raumklima

bosch_bfl524_drehteller_originalteil_index_und_mass

Read-only

Glas-Drehteller für Bosch BFL524MS0 nach Durchmesser und exakter E-Nr-Kompatibilität getrennt prüfen — Check the listed tray size separately from exact spare-part compatibility.

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": {
      "modell_belegt": "<modell_belegt>",
      "zubehoer_durchmesser_mm": "<zubehoer_durchmesser_mm>",
      "e_nr_liste": "<e_nr_liste>"
    },
    "name": "bosch_bfl524_drehteller_originalteil_index_und_mass"
  }
}

Input Schema

NameRequiredDescriptionDefault
e_nr_listeYesErsatzteilliste für die konkrete E-Nr einschließlich Index.
modell_belegtYesE-Nr mit Index und Modellzuordnung des konkreten Herstellernachweises stimmen überein?
zubehoer_durchmesser_mmYesDokumentierter Durchmesser des Angebots in mm, 0 bei fehlender Angabe.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/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 by structured data. The description adds the useful behavioral point that the diameter check and the E-Nr compatibility check are separate verdicts, but it says nothing about what the tool does with the supplied evidence or what a caller receives back.

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 compact sentence, front-loaded with the product and the two check dimensions, with no padding. The German/English duplication is mildly redundant but serves as a quick gloss, so it does not seriously hurt the sentence's efficiency.

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?

There is no output schema, so the description would need to say what a successful check yields — a verdict, a compatibility flag, or a passed-through assessment — and it does not. For a three-required-parameter evidence tool whose result is unspecified, an agent can call it but cannot predict the outcome or judge how to use it downstream.

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 carry their own German descriptions, including the enum values for e_nr_liste, so the schema does the heavy lifting. The description only reinforces that diameter and E-Nr are evaluated independently, adding marginal meaning beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a concrete resource (Glas-Drehteller für Bosch BFL524MS0) and two distinct axes (Durchmesser and exakte E-Nr-Kompatibilität), but the verb 'getrennt prüfen' is generic and does not say whether the tool looks up, validates, or records an evidence assessment — the readOnlyHint plus required inputs like 'modell_belegt' suggest an evidence-recording check, which the description never makes explicit. It also offers no differentiation from the many sibling check tools in the catalog.

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 instruction to check tray size 'separately' from exact spare-part compatibility is an implied usage constraint — it tells the agent not to conflate the two dimensions — but there is no statement of when to call this tool versus the sibling Prüfung/Beleg tools, and no prerequisites or exclusions are given.

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