Skip to main content
Glama

getecoback-raumklima

bosch_bfl524ms0_watt_anschlusswert_und_garleistung

Read-only

Bosch BFL524MS0: 800 W Mikrowellenleistung, 1270 W Anschlusswert und einen gemessenen Verbrauch auseinanderhalten — Separate cooking output, rated input and energy measured in use.

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": {
      "datenblatt_belegt": "<datenblatt_belegt>",
      "vorhandener_wert": "<vorhandener_wert>"
    },
    "name": "bosch_bfl524ms0_watt_anschlusswert_und_garleistung"
  }
}

Input Schema

NameRequiredDescriptionDefault
vorhandener_wertYesWelcher Wert soll eingeordnet werden?
datenblatt_belegtYesE-Nr mit Index und Modellzuordnung des konkreten Herstellernachweises stimmen überein?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/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 and scope are covered without the description's help. The description adds the substantive domain framing that three distinct watt figures exist and must not be conflated, but says nothing about permissions, rate limits, or what the response contains. With annotations carrying the behavioral profile, a 3 is appropriate.

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 leads with the model and the three concrete figures before the abstract instruction. The German/English duplication adds length but also serves as a gloss; nothing is padding in the sense of restating the title.

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

Completeness4/5

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

For a two-parameter, fully schema-documented read-only classification tool with no output schema, the description supplies enough to call it correctly. The only real gap is that it does not hint at the shape of the returned classification, which matters somewhat when no output schema exists.

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%: both 'vorhandener_wert' (with its four-value enum) and the boolean 'datenblatt_belegt' are documented in the schema itself. The description adds no format, default, or validation detail beyond what the schema already states, so the baseline of 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 the concrete artifact (Bosch BFL524MS0) and the specific task: keeping microwave cooking output (800 W), rated input (1270 W) and measured in-use consumption apart. That is a clear verb-plus-resource statement an agent can act on, though it does not name a sibling tool it should be preferred over.

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 is only implied: 'auseinanderhalten' signals this is the disambiguation tool when wattage figures are being confused, and the 'vorhandener_wert' enum encodes the cases. There is no explicit statement of when to use it versus the many sibling Bosch BFL524 lookups, and no exclusions or prerequisites.

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