Skip to main content
Glama

getecoback-raumklima

bosch_bfl524_watt_stufe_maximale_zeiteinstellung

Read-only

Die maximal einstellbare Zeit je Bosch BFL524 Leistungsstufe im Handbuch prüfen — Read the maximum selectable timer for each microwave output setting.

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>",
      "stufe_w": "<stufe_w>",
      "gewuenschte_min": "<gewuenschte_min>"
    },
    "name": "bosch_bfl524_watt_stufe_maximale_zeiteinstellung"
  }
}

Input Schema

NameRequiredDescriptionDefault
stufe_wYesAm Gerät abgelesene Leistungsstufe in Watt.
gewuenschte_minYesGeplante Einstelldauer in Minuten.
handbuch_belegtYesGenaue deutsche Geräteausführung BFL524MS0 und Anwendbarkeit des Dokuments 9001610906_F am Gerät geklärt?

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 safety and scope are covered. The description adds the meaningful detail that the answer is sourced from the manual ('im Handbuch prüfen') rather than from the appliance, which matters for trust in the result. It says nothing about what happens when the requested time exceeds the documented maximum, which is the core failure mode of this lookup.

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?

A single sentence keeps it front-loaded and scannable. However, the German and English halves are near-verbatim duplicates, so half the text is redundant padding rather than added information.

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?

With no output schema, the description should indicate what the lookup yields (e.g., the maximum permitted minutes for the given level, or a flag when the desired time exceeds it). It instead restates the query, leaving the return shape to inference, though the read-only, narrow scope keeps the gap modest.

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 (power level enum, desired minutes with 0–1440 bounds, and the handbuch_belegt applicability gate) are already fully documented in the schema. The description adds only the loose hint that the lookup is per power level, which the enum makes obvious anyway.

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 operation on a specific resource: looking up ('prüfen') the maximum selectable time per Bosch BFL524 power level, with the English gloss confirming the microwave output-setting scope. An agent can tell this is a manual-spec lookup rather than a device read. It stops short of 5 because it never distinguishes itself from the many other BFL524 lookup siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use or when-not-to-use guidance and no named alternative among the crowded BFL524 sibling set. The scenario (a user planning a timer duration at a given watt level) is only implied by the parameter set, not stated.

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