Skip to main content
Glama

getecoback-climate-weather

bosch_bfl524ms0_nische_geraetemass_unterscheiden

Read-only

Bosch BFL524MS0 prüfen: Nischenmaße, Gerätemaße und Garraummaße auseinanderhalten — Distinguish cabinet opening, outer body and cavity dimensions.

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>",
      "hoehe_mm": "<hoehe_mm>",
      "breite_mm": "<breite_mm>",
      "tiefe_mm": "<tiefe_mm>",
      "messbezug": "<messbezug>"
    },
    "name": "bosch_bfl524ms0_nische_geraetemass_unterscheiden"
  }
}

Input Schema

NameRequiredDescriptionDefault
hoehe_mmYesFreies Nischenmaß Höhe in Millimetern.
tiefe_mmYesFreies Nischenmaß Tiefe in Millimetern.
breite_mmYesFreies Nischenmaß Breite in Millimetern.
messbezugYesWie wurden die Maße erfasst?
modell_belegtYesE-Nr mit Index und Modellzuordnung des konkreten Herstellernachweises stimmen überein?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior2/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. The description adds nothing operational beyond intent: it never says what happens when messbezug is 'unklar' or modell_belegt is false, nor whether the call rejects, warns or simply classifies. For a five-required-parameter validation call, this leaves the agent guessing at the actual behaviour.

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 tightly built sentence, front-loaded with the model number and handing the core distinction forward before the English gloss. The bilingual restatement is mildly redundant but earns its place for a mixed-language catalogue; nothing else is wasted.

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?

Five required parameters and no output schema, so the description should at least say what 'prüfen' yields — a per-dimension verdict, a mismatch flag, or a corrected assignment. That return-side gap is unaddressed, though the input side is fully covered by the schema.

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 every parameter carries its own German description, including the messbezug enum, so the baseline is 3. The description's mention of the three measurement frames loosely maps onto the enum values but adds no new semantics about units, limits or what 'unklar' triggers.

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 specific subject (Bosch BFL524MS0), a specific action (prüfen / distinguish), and the exact conceptual split it operates on: cabinet opening (Nische), outer body (Gerätemaß) and cavity (Garraum). That verb+resource specificity is enough to tell it apart from siblings such as bosch_sbv4ebx00d_nische_tueroeffnung_abgleichen or stapelsaeule_nische_tiefe_versatz_vorderkanten, though no sibling is named explicitly.

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 'Nischenmaße, Gerätemaße und Garraummaße auseinanderhalten' implies the situation that calls for this tool: the agent has mixed up measurement references and needs them separated. There is no explicit when-not guidance, no statement of prerequisites (e.g. that the E-Nr must be confirmed first) and no pointer to an alternative sibling for related Bosch BFL524 checks.

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