Skip to main content
Glama

getecoback-climate-weather

bosch_tat8613_broetchenaufsatz_integriert_ersatzbeleg

Read-only

Den integrierten Brötchenaufsatz vom Nachweis eines losen Ersatzteils trennen — Identify the published rack configuration before buying an accessory.

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": {
      "modell_de_bestaetigt": "<modell_de_bestaetigt>",
      "angebot": "<angebot>",
      "ersatzteil_bestaetigt": "<ersatzteil_bestaetigt>"
    },
    "name": "bosch_tat8613_broetchenaufsatz_integriert_ersatzbeleg"
  }
}

Input Schema

NameRequiredDescriptionDefault
angebotYesArt des gefundenen Angebots.
modell_de_bestaetigtYesBosch TAT8613 und deutsche Herstellerunterlagen am betreffenden Gerät oder Angebot bestätigt?
ersatzteil_bestaetigtYesIst ein loser Aufsatz laut Herstellerunterlagen genau für die volle E-Nummer gelistet?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3/5.0
Behavior3/5

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

The readOnly and openWorldHint=false annotations already establish that this is a closed-world lookup with no side effects, and the description is consistent with that ('before buying' implies no purchase). It adds little beyond the annotations: nothing about what the answer is grounded in, how conflicting confirmations are handled, or what a resulting verdict looks like.

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?

It is short and front-loads the core distinction, so nothing is padded. However, the German/English split is redundant rather than complementary, and the English half's 'rack configuration' wording actively muddies what is being identified.

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?

With three required, fully documented parameters and no output schema, the definition says enough to fill the inputs but not enough to anticipate the result — it never states what verdict or proof the tool produces, which matters for a decision-support tool about part compatibility.

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 each parameter carries its own German explanation plus an enum, so the schema already does the work. The description only loosely echoes the concepts (integrated attachment, loose spare part) without adding any format, default, or value-selection guidance.

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

Purpose3/5

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

The German clause gives a verb-plus-resource ('Den integrierten Brötchenaufsatz ... vom Nachweis eines losen Ersatzteils trennen'), so the intent — distinguishing an integrated bread-roll attachment from a loose spare part — is inferable, but the English gloss renames the object as a 'rack configuration', which is a confusing mismatch and obscures the actual resource. It also never contrasts itself with sibling verification tools.

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 'before buying an accessory' supplies an implied context for use, and the German verb 'trennen' implies a disambiguation decision. There are no explicit when-not conditions, no prerequisites, and no named alternative tool the agent should pick instead.

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