Skip to main content
Glama

getecoback-raumklima

bosch_bfl524_autopilot_portion_und_programmtabelle

Read-only

Bosch AutoPilot: dokumentierte Speisegruppe, Portionsgewicht und Programmnummer zusammenlesen — Look up the listed food category and weight range for the exact AutoPilot programme.

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>",
      "speise": "<speise>",
      "menge_g": "<menge_g>",
      "zustand": "<zustand>"
    },
    "name": "bosch_bfl524_autopilot_portion_und_programmtabelle"
  }
}

Input Schema

NameRequiredDescriptionDefault
speiseYesTatsächliche Speisegruppe.
menge_gYesGewogenes Lebensmittel ohne Verpackung, 0 falls unbekannt.
zustandYesWofür soll das Automatikprogramm verwendet werden?
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

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 the safety profile is covered structurally. The description adds one piece of genuine context — that results are 'dokumentiert' / 'listed', i.e. only documented pairs are returned and the programme is 'exact' rather than interpolated — but says nothing about what happens for undocumented combinations or unknown values ('unbekannt' enum entries).

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 no filler; the German/English doubling is slightly redundant but reads as deliberate bilingual phrasing rather than padding.

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 four-required-parameter read-only lookup with no output schema, the description conveys both the inputs (food category, weight range) and the return (Programmnummer / exact AutoPilot programme). What is missing is modest: any mention of the zustand dimension or of how 'unbekannt' inputs are handled.

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 enums for speise and zustand, so the schema carries the parameter burden and baseline 3 applies. The description reinforces speise and menge_g but never mentions zustand (auftauen vs garen), which is arguably the field that selects between programmes, nor the handbuch_belegt prerequisite.

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 ('zusammenlesen' / 'Look up') and a specific resource (the documented Speisegruppe, Portionsgewicht and Programmnummer for the exact AutoPilot programme), so an agent can tell this is a documentation-table lookup rather than a device-control action. It does not name or contrast any of the many AutoPilot-adjacent siblings (e.g. autoprogramm_deckel_auftauen_garen, automatik_signal_waehrend_programm), so it falls short of full sibling differentiation.

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 by the phrase 'Look up the listed food category and weight range for the exact AutoPilot programme'. There is no explicit statement of when to prefer this over the sibling automat/programm tools, nor any exclusion such as 'do not use for actual programme execution'.

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