Skip to main content
Glama

getecoback-climate-weather

bosch_bfl524_autoprogramm_deckel_auftauen_garen

Read-only

Vorhandenen Deckel mit der offenen Auftau- oder abgedeckten Garvorgabe des Bosch-Programms abgleichen — Check whether the named Bosch programme lists an uncovered or covered vessel.

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>",
      "programm": "<programm>",
      "deckel": "<deckel>"
    },
    "name": "bosch_bfl524_autoprogramm_deckel_auftauen_garen"
  }
}

Input Schema

NameRequiredDescriptionDefault
deckelYesBeobachtete und für die Mikrowelle freigegebene Ausstattung.
programmYesDie tatsächlich gewählte Programmnummer.
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.4/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, and the description is consistent with a pure comparison check. It adds no context on what the comparison yields, how an 'unbekannt' programme or 'nicht_belegt' lid is handled, or whether a mismatch blocks operation.

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 with the German statement followed by an English gloss; no filler. The bilingual duplication is slightly redundant but serves disambiguation rather than padding.

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?

For a three-required-parameter read-only check with no output schema, the description should indicate what verdict comes back (e.g. lid requirement met or not). It explains the comparison but not the outcome, leaving a gap an agent must discover by calling.

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 coverage is 100% with documented enums for deckel and programm, so the schema carries the parameter burden. The description only restates the lid/programme pairing and adds nothing about the handbuch_belegt gate parameter, which is the least self-explanatory of the three.

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?

States a specific verb (abgleichen/check) and the two things being compared: the observed lid and the Bosch programme's open/covered specification. It is distinguishable from siblings like the portion/programme-table tool, though the dense bilingual phrasing takes a second read.

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: an agent can infer this is the tool for verifying whether a chosen programme requires an uncovered or covered vessel. There is no explicit when-to-use, no exclusion, and no pointer to a sibling for related programme questions.

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