Skip to main content
Glama

getecoback-raumklima

braun_zerkleinerer_eis_bc_mc_und_messer_unterscheidung

Read-only

Unterscheidet die Eis-Freigabe in den beiden Braun Anleitungen nach Becherkennung und eigenem Eismesser — Distinguish the Braun ice-use conditions by vessel code and dedicated ice blade.

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>",
      "code": "<code>",
      "messer": "<messer>",
      "teile_geprueft": "<teile_geprueft>"
    },
    "name": "braun_zerkleinerer_eis_bc_mc_und_messer_unterscheidung"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesBecherkennung der passenden Anleitung.
motorYesExaktes Gerät der deutschen Braun Unterlage.
messerYesOriginales Messer laut genau diesem Handbuch.
teile_geprueftYesVorhandener Aufsatz und Teilzuordnung sind dokumentiert.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

readOnlyHint=true and openWorldHint=false already establish this is a safe, closed-world read, so the bar is lower. The description adds that the operation is a differentiation between two manuals' ice conditions, but says nothing about what the result looks like (a verdict, a mapping, a per-chart breakdown) or what happens with the 'offen' enum values.

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?

One front-loaded sentence that puts the object of the comparison first. The only waste is the full German/English duplication of the same content, which adds length without adding information.

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?

With 100% enum-documented parameters and read-only annotations, the inputs are well covered and no output schema is expected. Still, for a tool whose entire value is producing a distinguishing verdict, the description does not indicate what the caller receives or how the two axes combine into an answer.

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 all four parameters carry enum-backed descriptions, so the baseline is 3. The description echoes two of them ('Becherkennung', 'eigenes Eismesser'), which confirms their relevance to the ice release decision but adds no syntax or interpretation beyond the schema.

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 operation ('Unterscheidet die Eis-Freigabe') on a specific resource (the two Braun manuals' ice-use conditions), and identifies the two discriminating axes: vessel code and dedicated ice blade. An agent can tell this is a comparison/classification lookup rather than a general Braun query, though it does not name the near-identical sibling about Behälterkennzeichen.

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 statement of when to call this versus the many sibling Braun Zerkleinerer tools (e.g. braun_zerkleinerer_ca_mc_hc_bc_behaelterkennzeichen), and no exclusions or prerequisites. The phrase 'in den beiden Braun Anleitungen' implies scope but leaves the choice between siblings to inference.

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