Skip to main content
Glama

getecoback-raumklima

bosch_bfl524_memory_einzelschritt_oder_automatik

Read-only

Beim Bosch BFL524 prüfen, ob ein einzelner manueller Ablauf im vorhandenen Memory-Platz gespeichert werden kann — Check whether the intended routine fits the single memory slot.

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>",
      "ablauf": "<ablauf>",
      "zielspeicher_anzahl": "<zielspeicher_anzahl>"
    },
    "name": "bosch_bfl524_memory_einzelschritt_oder_automatik"
  }
}

Input Schema

NameRequiredDescriptionDefault
ablaufYesZu speichernder Ablauf.
handbuch_belegtYesGenaue deutsche Geräteausführung BFL524MS0 und Anwendbarkeit des Dokuments 9001610906_F am Gerät geklärt?
zielspeicher_anzahlYesAnzahl gleichzeitig benötigter Speicherplätze.

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 is covered. The description adds device-model and slot-scoping context, but says nothing about what the check returns (fit/no-fit, slot count, error) or about the manual_belegt precondition it depends on.

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 German sentence is front-loaded and specific, but the English half is essentially a translation of the first rather than new information, so the definition carries redundancy without added decision value.

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 advisory check with no output schema, the agent still lacks the outcome semantics and how manuell_mehrere_stufen or automatik should be interpreted against a 'single slot' premise. The core intent is present but the definition stops short of being fully actionable.

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 the parameters are already documented and a 3 is the baseline. The description's 'single memory slot' wording actually conflicts slightly with zielspeicher_anzahl (1–25 slots) and with the enum values manuell_mehrere_stufen and automatik, adding a bit of noise rather than meaning.

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?

Names a concrete verb (prüfen) and a concrete resource (Memory-Platz on the Bosch BFL524), so the agent knows this is a feasibility check rather than a configuration change. It does not distinguish itself from the many sibling BFL524 lookup tools, and the framing as 'single manual routine' sits awkwardly with the name's 'Einzelschritt oder Automatik'.

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 guidance on when to call this versus sibling tools, nor any prerequisite or exclusion. The only implicit trigger is 'when you want to know if a routine fits', which the agent must infer from the sentence itself.

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