Skip to main content
Glama

getecoback-raumklima

bosch_ergomixx_e_nummer_ausfuehrung_handbuch

Read-only

Ordnet einer vollständig abgelesenen deutschen Bosch ErgoMixx E-Nr. die Anleitung und Service-Seite zu (MSM67170/02, MS6CA4150/02, MS6CB61V1/01) — Route a full German Bosch ErgoMixx E-number to the correct manual and service page.

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

Input Schema

NameRequiredDescriptionDefault
e_nummerYesVollständige deutsche Bosch E-Nr. einschließlich Index.
typenschild_exaktYesGrundmodell und Index sind am Typenschild der konkreten Einheit geprüft.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already state readOnlyHint=true and openWorldHint=false, so the safety profile is clear. The description adds that the result is a manual and service page for specific model numbers, but it does not disclose what happens with the 'offen' value, an unsupported E-number, or a false typenschild_exakt flag.

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?

The description is compact and front-loads the core action before the English translation. The bilingual duplication is somewhat redundant, but the content is clear and contains no obvious filler.

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-parameter lookup tool, the description covers the main intent and supported model examples. However, because there is no output schema, it should say more about what the returned manual/service page information looks like, and it leaves edge cases such as 'offen' and typenschild_exakt=false unexplained.

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%, so the baseline is 3. The description reinforces that the E-number must be fully read off and includes example values, but it does not add meaning beyond the schema for the 'offen' enum value or explain the role of typenschild_exakt.

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 uses a specific verb and resource: it routes a full German Bosch ErgoMixx E-number to the correct manual and service page, and it gives concrete example E-numbers. It is clear what the tool does, but it does not explicitly distinguish itself from sibling tools that also deal with Bosch ErgoMixx identifiers.

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 phrase 'vollständig abgelesenen' and 'full German' implies the tool should be used only when the entire E-number including index is known. However, there is no explicit when-not guidance, no mention of alternatives, and no explanation of the 'offen' enum value or what to do when the Typenschild check is negative.

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