Skip to main content
Glama

getecoback-raumklima

bosch_bfl524_glas_drehteller_zustand_betriebssperre

Read-only

Einen fehlenden, nicht eingerasteten oder gesprungenen Drehteller vor der Nutzung einordnen — Gate use on an undamaged and properly seated manufacturer tray.

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>",
      "zustand": "<zustand>"
    },
    "name": "bosch_bfl524_glas_drehteller_zustand_betriebssperre"
  }
}

Input Schema

NameRequiredDescriptionDefault
zustandYesBeobachteter Zustand des Drehtellers.
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.6/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. The description adds the gating behavior ('Gate use'), which is useful, but it does not explain the result semantics, such as what happens when the tray is missing or damaged.

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?

The description is a single front-loaded sentence with no wasted framing. The bilingual restatement is slightly redundant but helps clarify the gating intent without adding bloat.

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?

This is a simple two-parameter read-only classifier with full schema coverage and annotations. The description covers the purpose and gating context well; the main remaining gap is what the tool returns or how a bad condition affects operation, but no output schema exists to demand that.

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 schema already documents both parameters and the enum values. The description does not add meaning beyond the schema, making the baseline score of 3 appropriate.

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 action ('einordnen') and resource ('Drehteller'), plus the condition to assess: missing, not seated, or cracked. It is clear but does not explicitly contrast with sibling tools, so it stops short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'vor der Nutzung' and 'Gate use on an undamaged...' clearly establishes when to use this tool: before operating the appliance, as a precondition check. It does not name alternatives or when-not conditions, but the usage context is unambiguous.

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