Skip to main content
Glama

getecoback-climate-weather

bosch_sks62e32eu_korbmerkmal_oder_sonderzubehoer

Read-only

Liest einen Korbhinweis aus der Gerätebeschreibung getrennt von gelistetem Sonderzubehör — Distinguish a documented basket feature from separately listed special accessories.

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": {
      "teil": "<teil>",
      "modell_de_belegt": "<modell_de_belegt>",
      "lieferung_bestaetigt": "<lieferung_bestaetigt>"
    },
    "name": "bosch_sks62e32eu_korbmerkmal_oder_sonderzubehoer"
  }
}

Input Schema

NameRequiredDescriptionDefault
teilYesVorliegende Bezeichnung.
modell_de_belegtYesExakte deutsche Produktunterlage für das Angebot verwendet?
lieferung_bestaetigtYesDer Verkäufer oder eine eigene Bestandsliste weist das konkrete Teil dieser Lieferung zu.

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 declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds that the source of truth is the device description and that listed special accessories are treated separately, which is useful context; however it does not say how ambiguous or undocumented cases are handled or how the boolean evidence inputs drive the outcome.

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?

Two short clauses with the discriminating question front-loaded, no filler. The German/English duplication is mildly redundant, and the mixed-language dash construction reads slightly awkwardly, but nothing is wasted.

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 read-only classification tool with three fully documented parameters this is adequate, but there is no output schema, so the description should state what the tool returns and how the classification is expressed. As written, an agent knows the question being answered but not the shape or decisiveness of the answer.

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 every parameter carries its own description, so the baseline is 3. The description adds only the high-level notion of separating documented features from listed accessories; it does not explain the enum values (vario_besteckkorb, tassenetageren, sgz3003, unbekannt) or the role each evidence flag plays.

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 names a specific verb (read/distinguish) and a specific resource pair: a documented basket feature (Korbhinweis aus der Gerätebeschreibung) versus separately listed special accessories. It is clear what question the tool answers, though it never states what a call returns (a verdict, a label, a classification), which keeps it from a full 5.

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 only implied by the disambiguation framing — an agent can infer it should call this when it must decide whether a part belongs to the basket or is a separate accessory. There is no explicit when-to-use trigger, no when-not condition, and no alternative tool named among the many sibling tools.

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