Skip to main content
Glama

getecoback-raumklima

bosch_bfl524_demo_modus_anzeige_ohne_garfunktion

Read-only

Beim dokumentierten Demo-Modus die bedienbare Anzeige von der tatsächlichen Garfunktion trennen — Recognize the documented showroom mode without diagnosing a failure.

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>",
      "modus": "<modus>",
      "oberflaeche_bedienbar": "<oberflaeche_bedienbar>"
    },
    "name": "bosch_bfl524_demo_modus_anzeige_ohne_garfunktion"
  }
}

Input Schema

NameRequiredDescriptionDefault
modusYesIn den Grundeinstellungen zuverlässig gelesener Status.
handbuch_belegtYesGenaue deutsche Geräteausführung BFL524MS0 und Anwendbarkeit des Dokuments 9001610906_F am Gerät geklärt?
oberflaeche_bedienbarYesDisplay beziehungsweise Tasten wirken bedienbar.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3/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 and the bar is lower. The description adds the useful behavioral boundary that this is recognition, not fault diagnosis, but says nothing about what the tool returns or how conflicting inputs (e.g. demo active yet display operable) are resolved.

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?

The definition is short and front-loads the German framing before the English gloss, which is acceptable for a bilingual catalog. The two halves restate essentially the same idea, so the second clause is partially redundant rather than additive.

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 three fully described required parameters and read-only annotations, most of the calling contract is in structured fields. What is missing is the decision logic or expected conclusion (what a 'demo active but display operable' result means), which matters for a tool whose whole purpose is an assessment; no output schema exists to cover that gap.

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% with all three parameters documented, including the 'nicht_gelesen' enum state and the manual/device-variant clarification. The description adds no parameter-level meaning beyond the schema, so the baseline 3 applies.

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 the subject (documented demo/showroom mode) and the operation (separating an operable display from the real cooking function), plus a negative scope (not a failure diagnosis). However, the verb 'trennen' is abstract and the tool name is an opaque compound, so an agent cannot tell concretely what the tool produces or how it differs from the many similarly named Bosch siblings without opening the schema.

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?

'Recognize the documented showroom mode without diagnosing a failure' implies the situation (a unit appears to be in demo mode) and rules out a failure-diagnosis use case. It never states prerequisites, what to do when modus is 'nicht_gelesen', or names any alternative tool, so guidance is implied rather than explicit.

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