Skip to main content
Glama

getecoback-raumklima

braun_zerkleinerer_ca_mc_hc_bc_behaelterkennzeichen

Read-only

Ordnet Braun Zerkleinerer an ihrer Unterlagenkennung ca, mc, hc oder bc zu — Identify a Braun chopper by its documented ca, mc, hc or bc vessel code.

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

Input Schema

NameRequiredDescriptionDefault
codeYesKennzeichen aus der Abbildung des konkreten Aufsatzes.
motorYesExaktes Gerät der deutschen Braun Unterlage.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior2/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 nothing beyond that: it does not explain how the 'offen' enum value is treated, what the mapping result looks like, or what happens for unknown motor/code combinations.

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?

Short, but the same sentence is given twice in German and English with no additional information in either version. The duplicated translation wastes half the description's length without adding 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 simple two-enum lookup tool with a fully documented schema, the definition is minimally adequate. However, without an output schema, the description never indicates what is returned for a given motor/code pairing or how ambiguous or 'offen' inputs are resolved.

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 coverage is 100% and both parameters carry descriptive enum documentation, so the baseline is 3. The description merely repeats the code enum values already present in the schema and says nothing about the motor parameter or the 'offen' fallback.

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?

States a specific verb and resource: identify/assign a Braun chopper by its vessel code (ca, mc, hc, bc). An agent can tell what the tool does, but the description does not distinguish it from closely related siblings such as braun_zerkleinerer_eis_bc_mc_und_messer_unterscheidung, which apparently also deals with these codes.

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 use this over the many other Braun Zerkleinerer tools, nor any prerequisite or exclusion. The agent must infer the usage context entirely from the name and enum values.

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