Skip to main content
Glama

getecoback-raumklima

bosch_tat8613_aufbacken_max_stufe_aufsatzbedingungen

Read-only

Maximale Aufbackstufe für den Brötchenaufsatz und Parallelbetrieb des Röstschachts prüfen — Verify the rack mode and its published maximum level.

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": {
      "modell_de_bestaetigt": "<modell_de_bestaetigt>",
      "aufsatz_ausgefahren": "<aufsatz_ausgefahren>",
      "parallel_toasten": "<parallel_toasten>",
      "folie_oder_tropfendes": "<folie_oder_tropfendes>",
      "stufe": "<stufe>"
    },
    "name": "bosch_tat8613_aufbacken_max_stufe_aufsatzbedingungen"
  }
}

Input Schema

NameRequiredDescriptionDefault
stufeYesAm Gerät lesbare Stufe.
parallel_toastenYesGleichzeitig Toast im Röstschacht vorgesehen?
aufsatz_ausgefahrenYesIntegrierter Brötchenaufsatz ist ausgefahren?
modell_de_bestaetigtYesBosch TAT8613 und deutsche Herstellerunterlagen am betreffenden Gerät oder Angebot bestätigt?
folie_oder_tropfendesYesAlufolie oder tropfendes Aufbackgut vorgesehen?

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 the safety profile is covered and the bar is lower. The description adds that this is a check against 'published' maximum levels rather than a measurement, but it does not say what the verdict looks like or what happens when folie_oder_tropfendes or parallel_toasten is true.

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?

One short sentence, but roughly half of it is a duplicate English translation that conveys less than the German original. The bilingual restatement costs space without adding information, and the conditional nature of the check is not front-loaded.

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 read-only tool with five fully described required booleans/numbers and no output schema, the description should indicate what a valid versus invalid condition set means for the reported maximum. It stops at the topic and leaves the decision logic — the actual value of the tool — unexplained.

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 every parameter including the 0-9 stufe bound is already documented and the baseline is 3. The description only hints that the stufe is evaluated jointly with attachment state and Röstschacht use, without adding interpretation rules beyond what the schema fields state.

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 German half states a concrete verb and resource: verifying the maximum aufback level for the Brötchenaufsatz together with parallel Röstschacht operation. The English half is a loose, partly inconsistent rendering ('rack mode' for 'Aufsatzbedingungen') and neither half names a distinguishing sibling such as the broetchenaufsatz_integriert_ersatzbeleg or kruemelschublade tools.

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?

The definition never says when to reach for this tool versus the other bun-attachment siblings, nor when the question falls outside its scope. A user asking about the tray in general could plausibly land on three or four different tools with no routing hint here.

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