Skip to main content
Glama

getecoback-climate-weather

bosch_mikrowelle_bfl_bel_grill_modellbeleg

Read-only

Die deutsche Bosch BFL524MS0 und BEL524MS0 bei einem angebotenen Grillmodus unterscheiden — Distinguish the solo microwave and grill variant before purchase.

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": {
      "laut_typenschild": "<laut_typenschild>",
      "quelle_gilt": "<quelle_gilt>",
      "grill_benoetigt": "<grill_benoetigt>"
    },
    "name": "bosch_mikrowelle_bfl_bel_grill_modellbeleg"
  }
}

Input Schema

NameRequiredDescriptionDefault
quelle_giltYesE-Nr mit Index und Modellzuordnung des konkreten Herstellernachweises stimmen überein?
grill_benoetigtYesIst ein eigener Grillmodus für die Nutzung erforderlich?
laut_typenschildYesTatsächlich gelesenes Modell.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3/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 and the bar is lower. Still, the description gives no insight into how the three inputs are combined into a resolution, what happens when 'laut_typenschild' is 'ungeklaert', or what the verdict looks like — the core behavior of a classification tool is left undisclosed. With no output schema either, the agent cannot infer the outcome.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single short line with no padding, but it is a grammatical fragment and presents the same content twice in German and English, which doubles length without adding information. The decision-scope qualifier is present but not clearly front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a decision/classification tool with three required inputs, no output schema, and rich ambiguous inputs (ungültige Quelle, unklares Typenschild), the description should explain the resolution logic or the expected answer shape. It supplies only an objective, leaving the agent to guess how input combinations map to a recommendation.

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 a German description plus an enum for 'laut_typenschild', so the schema does the heavy lifting. The tool description mentions none of the three inputs (nameplate reading, source validity, grill requirement) and adds no semantics beyond what the schema states. Baseline 3 applies.

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 verb ('unterscheiden') and two concrete resources (Bosch BFL524MS0 vs BEL524MS0), so the agent knows this is a model-variant disambiguation tool. The qualifying clause 'bei einem angebotenen Grillmodus' narrows the operation, though the fragmentary grammar ('Die deutsche Bosch ... unterscheiden') leaves it slightly cryptic about what the tool actually produces. Sibling tools like bosch_bfl524ms0_nische_geraetemass_unterscheiden follow a similar 'unterscheiden' pattern and are not addressed.

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 context is implied by 'before purchase' (vor dem Kauf), giving the agent a decision-point trigger. However, there is no statement of when NOT to use it, no preconditions (e.g. required nameplate photo or E-Nr), and no named alternative for related Bosch BFL/BEL questions among the many siblings.

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