Skip to main content
Glama

getecoback-climate-weather

braun_mq30_mqs230_kupplung_wellenschnitt_gerade

Read-only

Vergleicht die konkrete Braun Kupplung von 500-ml-MQ 30 und MQS 230 nach Wellenschnitt oder geradem Anschluss — Compare the actual coupling profile of the Braun MQ 30 and MQS 230 choppers.

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>",
      "motoranschluss": "<motoranschluss>",
      "zubehoer": "<zubehoer>"
    },
    "name": "braun_mq30_mqs230_kupplung_wellenschnitt_gerade"
  }
}

Input Schema

NameRequiredDescriptionDefault
motorYesExaktes Gerät der deutschen Braun Unterlage.
zubehoerYesExakte Braun Zubehörkennung.
motoranschlussYesFür die eigene Motoreinheit bestätigter Anschluss.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/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 and the description does not contradict it. The description adds only the thematic scope (coupling type by Wellenschnitt/gerade); it says nothing about what the comparison actually yields, whether an 'offen' value triggers a fallback, or how ambiguity is resolved.

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 compact bilingual sentence with the domain scope front-loaded and no filler. The German/English duplication is a minor redundancy, but it plausibly serves the German-language source vocabulary the enums use.

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?

With three fully described required enum parameters, a read-only annotation profile, and no output schema, the remaining obligation is modest. The main gap is that the description never indicates what the comparison produces (a confirmation, a mismatch verdict, or a value list), which for a tool whose whole purpose is 'comparing' leaves the outcome underspecified.

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 three parameters are enums with their own descriptions, so the schema carries the parameter meaning and a baseline of 3 applies. The description reinforces the domain framing (MQ 30 / MQS 230 choppers, Wellenschnitt vs. gerade) but adds no detail on how 'offen' should be chosen or how motor and zubehoer interact.

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 verb ('Vergleicht' / 'Compare') and a specific resource ('die konkrete Braun Kupplung ... nach Wellenschnitt oder geradem Anschluss'), scoped to two named device families (MQ 30, MQS 230). An agent can tell this is a coupling-type verification tool, but it never distinguishes itself from plausibly similar siblings such as 'abluftanschluss_kupplung_abgleichen' or the MQ7035XBI attachment tools.

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 phrasing 'Vergleicht ... die konkrete ... Kupplung' suggests it is for confirming which coupling (shaft-cut vs. straight) a given motor/attachment combination actually has. There is no explicit when-to-use, when-not-to-use, or named alternative, and no stated precondition such as consulting the German Braun underlay first.

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