Skip to main content
Glama

getecoback-raumklima

braun_zerkleinerer_topf_mikrowelle_piktogramm_bezug

Read-only

Liest das Braun Mikrowellenverbot für den dokumentierten Zerkleinerertopf und grenzt andere Gefäßrollen ab — Read Braun’s microwave exclusion for the mapped chopper bowl and leave other vessels unresolved.

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": {
      "motor": "<motor>",
      "gefaess": "<gefaess>",
      "modell_und_teil_belegt": "<modell_und_teil_belegt>"
    },
    "name": "braun_zerkleinerer_topf_mikrowelle_piktogramm_bezug"
  }
}

Input Schema

NameRequiredDescriptionDefault
motorYesExaktes Gerät der deutschen Braun Unterlage.
gefaessYesGenau betrachtete Gefäßrolle.
modell_und_teil_belegtYesAbbildung gehört zur bestätigten Ausführung und das Gefäß ist zugeordnet.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/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 genuine behavioral context beyond that: it reads a prohibition specifically and deliberately leaves other vessel roles unresolved rather than guessing. However, with no output schema it never states what a 'read' returns (a flag, a pictogram reference, an unknown state) or how enum value 'offen' is handled, which is a real gap for a no-output tool.

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 single sentence is front-loaded with the core action and is easy to parse. But the German and English halves say the same thing twice, roughly doubling length without adding information. Every clause earns its place content-wise, yet the bilingual duplication is avoidable bloat.

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?

Inputs are fully documented and only three are required, so the calling mechanics are covered. What is missing is the result contract: without an output schema, the description should say what a positive read, a negative read, and an 'offen' (undetermined) input yield. The scoping rule is stated, but the outcome an agent should expect is not.

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% and both enums carry their own descriptions, so the schema already does the parameter work. The description adds only mild framing ('dokumentiert', 'mapped') that echoes the 'modell_und_teil_belegt' mapping condition without new syntax or constraint detail. Baseline 3 is 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 concrete verb ('liest' / 'Read') and a concrete resource ('Braun Mikrowellenverbot' for the documented 'Zerkleinerertopf'), so the agent knows exactly which fact is being retrieved. It also signals its boundary by saying other vessel roles are explicitly left unresolved, which separates it from sibling vessel-recognition tools. It stops short of naming any alternative tool, so it is clear but not fully disambiguated.

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: the clause 'grenzt andere Gefäßrollen ab' / 'leave other vessels unresolved' tells the agent this tool is scoped to one vessel role, which hints at when it applies. There is no explicit statement of prerequisites (e.g. that 'modell_und_teil_belegt' must be true) or of which sibling to use for the other vessel roles. The agent must infer routing from the name and the negation.

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