Skip to main content
Glama

getecoback-climate-weather

bosch_ergomixx_mixfuss_oder_universalzerkleinerer_aufgabe

Read-only

Ordnet gekochtes Mixgut und ausdrücklich genanntes rohes Hackgut dem Bosch Mixfuß oder Universalzerkleinerer zu — Route cooked blending and named raw chopping jobs to the appropriate Bosch attachment.

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": {
      "e_nummer": "<e_nummer>",
      "aufgabe": "<aufgabe>",
      "aufsatz_im_haushalt_belegt": "<aufsatz_im_haushalt_belegt>"
    },
    "name": "bosch_ergomixx_mixfuss_oder_universalzerkleinerer_aufgabe"
  }
}

Input Schema

NameRequiredDescriptionDefault
aufgabeYesIn der Bosch Anleitung unterschiedene Aufgabe.
e_nummerYesVollständige deutsche Bosch E-Nr. einschließlich Index.
aufsatz_im_haushalt_belegtYesDer zugeordnete Aufsatz ist konkret und vollständig vorhanden.

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 and the description only needs to add routing context, which it does by framing the tool as an assignment decision. It does not disclose what the tool returns (which attachment was chosen), how the 'offen' E-Nr. or 'andere_aufgabe' enum values are handled, or what happens when the attachment is not present in the household. With annotations carrying the safety burden, a 3 is appropriate.

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 definition is short and front-loaded, but the German sentence and the English sentence are near-verbatim duplicates, so roughly half the text is redundant. The core routing rule is clear; the bilingual restatement does not add 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?

For a three-parameter, all-required routing tool with no output schema, the description covers the decision rule but not the outcome. An agent still cannot tell what the tool produces or how the boolean availability flag interacts with the routing decision, which is the main remaining gap.

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 are documented, so the baseline is 3. The description adds modest meaning by mapping the cooked/raw distinction onto the aufgabe enum and by stressing that raw chopping must be explicitly named. It says nothing about the role of aufsatz_im_haushalt_belegt, which is the parameter most likely to change the outcome.

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 states a specific verb (zuordnen/route) and a specific resource (Mixfuß vs. Universalzerkleinerer), and it splits the input space into cooked blending versus explicitly named raw chopping. That is enough for an agent to know this is an attachment-selection tool rather than a manual lookup. It does not name any sibling tool, so differentiation from the many other Bosch attachment tools is left implicit.

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 implied by the two qualifying conditions: cooked Mixgut, or raw Hackgut that is explicitly named. The word 'ausdrücklich' signals a real boundary (unnamed raw chopping is out of scope), which is useful. However, no alternative tool is named and no explicit when-not case or prerequisite is stated, so the agent must infer what to do for the excluded cases.

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