Skip to main content
Glama

getecoback-raumklima

bosch_ergomixx_set_lieferumfang_zubehoerrolle

Read-only

Liest den deutschen Bosch ErgoMixx Listen-Lieferumfang für die gewählte Zubehörrolle — Check the listed accessory role in an exact German Bosch ErgoMixx bundle.

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>",
      "teil": "<teil>",
      "originalangebot": "<originalangebot>"
    },
    "name": "bosch_ergomixx_set_lieferumfang_zubehoerrolle"
  }
}

Input Schema

NameRequiredDescriptionDefault
teilYesTeil, dessen Lieferumfang geprüft wird.
e_nummerYesVollständige deutsche Bosch E-Nr. einschließlich Index.
originalangebotYesVerglichen wird das veröffentlichte Bosch Set, nicht der Bestand einer gebrauchten Schachtel.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already establish that this is a read-only, closed-world lookup. The description adds that it checks the listed scope of delivery in an exact German Bosch bundle, but does not describe response shape, limits, or other behavioral details.

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 definition is short and front-loaded, with the German and English versions conveying the same core meaning. The bilingual repetition is somewhat redundant but does not obscure the tool's function.

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 simple three-parameter read-only lookup with full schema coverage and annotations, the description is largely sufficient. It could be improved by clarifying the expected result, especially since no output schema is provided.

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%, so all three parameters are already documented in the input schema. The description reinforces that the lookup applies to a selected accessory role in an exact German bundle, but adds little meaning beyond the schema.

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 read operation: it reads the German Bosch ErgoMixx list scope of delivery for the selected accessory role. This distinguishes it from broader compatibility or manual lookup siblings, though it does not explicitly name an alternative tool.

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

Usage Guidelines2/5

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

The description explains what the tool checks, but gives no explicit guidance about when to use it instead of related Bosch ErgoMixx compatibility or manual tools. There are no exclusions, prerequisites, or alternative-routing instructions.

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