Skip to main content
Glama

getecoback-raumklima

bosch_mixfuss_ersatzgefaess_boden_und_behaelterrolle

Read-only

Prüft, ob ein Ersatzgefäß beim Bosch Mixfuß einen ebenen Boden hat und kein Universalzerkleinerer-Behälter ist — Check the bottom and vessel role before using another vessel with the Bosch blending shaft.

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>",
      "gefaess": "<gefaess>",
      "boden": "<boden>"
    },
    "name": "bosch_mixfuss_ersatzgefaess_boden_und_behaelterrolle"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodenYesVon außen oder ohne Betrieb dokumentierter Innenboden.
gefaessYesKonkreter Behälter.
e_nummerYesVollständige deutsche Bosch E-Nr. einschließlich Index.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false, and the description adds the two concrete pass/fail criteria being checked: flat bottom and not a universal chopper container. However, it does not explain what the check returns, how failures are reported, or what the agent should do with the result, and no output schema exists to cover that gap.

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 compact sentence that front-loads the check and its criteria. The bilingual repetition adds some length, but the content remains focused and every clause contributes to the purpose.

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 read-only diagnostic tool, the description supplies purpose and usage context but omits return-value semantics. With no output schema, an agent cannot tell whether the tool returns a boolean, a reason, or follow-up instructions. Otherwise the definition is adequate for invoking the tool.

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%, with enum values documented for all three parameters. The description maps naturally to the 'boden' and 'gefaess' concepts but does not mention 'e_nummer' or add syntax or interpretation beyond the schema. Baseline 3 is appropriate because the schema carries the parameter semantics.

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, 'Prüft', and a precise resource/condition: whether a replacement vessel for the Bosch Mixfuß has a flat bottom and is not a universal chopper container. The English clause reinforces the same check. It does not name a sibling, but the purpose is clearly distinguishable from a general vessel-compatibility lookup.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says to check the bottom and vessel role 'before using another vessel with the Bosch blending shaft', giving a clear usage context. It also implicitly excludes universal chopper containers. It does not name an alternative tool or spell out when not to use it, but the guidance is stronger than a bare implied-use statement.

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