Skip to main content
Glama

getecoback-climate-weather

stabmixer_getriebedeckel_reinigung_spuelmaschine

Read-only

Prüft beim Bosch oder Braun Stabmixer, ob Motorteil oder Zerkleinerer-Getriebedeckel in die Spülmaschine darf, fließendes Wasser verträgt oder feucht abgewischt wird — Check dishwasher, rinse or wipe guidance for the exact Bosch or Braun part.

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": "<handbuch>",
      "teil": "<teil>"
    },
    "name": "stabmixer_getriebedeckel_reinigung_spuelmaschine"
  }
}

Input Schema

NameRequiredDescriptionDefault
teilYesBelegtes Einzelteil, nicht das komplette Set.
handbuchYesBelegte Geräteanleitung.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/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 real value by disclosing the answer space: the result is one of three verdicts (dishwasher-safe, rinse under running water, or damp-wipe only). It does not explain what happens when the part or manual is unknown, which the 'offen' enum values hint at.

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?

A single front-loaded sentence with the verb and scope first, followed by the bilingual restatement. The German/English duplication is a deliberate pattern but does add length without new information.

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?

For a read-only two-parameter lookup with a fully described enum schema and no output schema, the description gives enough to call it correctly and to know the shape of the answer. Only the fallback behavior for unknown parts/manuals is left unstated.

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 are enums with their own descriptions, so the schema carries the parameter burden. The description only names two of the ten part values as examples, adding little beyond the schema and slightly under-representing the enum's breadth.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (prüft/check) plus the exact resource: dishwasher/rinse/wipe suitability for the motor part or chopper gear cover of Bosch or Braun hand blenders. The brand and part scoping makes it clearly distinguishable from siblings like beurer_ks34_reinigung_feuchtes_tuch_kein_wasserbad or wasserkocher_twk8613p_spuelmaschine_basis_kanne_sieb.

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?

The description implies when to use it (you have a Bosch/Braun hand-blender part and need a cleaning verdict), but it never states exclusions or points to an alternative tool for other brands or other part types. The agent must infer that non-Bosch/Braun appliances are out of scope.

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