Skip to main content
Glama

getecoback-raumklima

saros10r_zubehoerset_bedarf_nach_teilrollen

Read-only

Entscheide bei vorhandenen brauchbaren Ersatzteilen, welche unterschiedlichen Rollen des Original-Sets für den Saros 10R überhaupt benötigt werden — Match a confirmed Saros 10R kit against separate missing part roles

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_bestaetigt": "<modell_bestaetigt>",
      "filter_fehlt": "<filter_fehlt>",
      "seitenbuerste_fehlt": "<seitenbuerste_fehlt>",
      "abdeckung_fehlt": "<abdeckung_fehlt>",
      "sonstiger_kaufbedarf": "<sonstiger_kaufbedarf>"
    },
    "name": "saros10r_zubehoerset_bedarf_nach_teilrollen"
  }
}

Input Schema

NameRequiredDescriptionDefault
filter_fehltYesEin zusätzlicher Roboterfilter wird begründet benötigt
abdeckung_fehltYesDie passende Hauptbürstenabdeckung wird begründet benötigt
modell_bestaetigtYesSaros 10R und offiziell gelistetes Zubehörset für den 10R auf dem Typenschild oder in den Unterlagen zum beobachteten Gerät bestätigt
seitenbuerste_fehltYesEine Seitenbürste wird begründet benötigt
sonstiger_kaufbedarfYesEin weiteres Teil aus dem Set wird nachweislich benötigt

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?

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds the meaningful precondition that the model and official kit must be confirmed before matching, but says nothing about how the resulting role determination is expressed or whether the answer is per-part or aggregate.

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?

The one-sentence description is front-loaded with the verb, but it is given twice in German and English, which pads the text without adding information. The em-dash bilingual pairing also makes the actual scope harder to parse at a glance.

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 no output schema, the description should explain what the decision looks like (e.g. which roles/parts are needed), and it only gestures at this. For a five-required-parameter decision tool the schema carries the input side well, but the result side is left underspecified.

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 all five booleans (filter_fehlt, seitenbuerste_fehlt, abdeckung_fehlt, sonstiger_kaufbedarf, modell_bestaetigt) are already fully documented in the schema. The description adds only the general framing of matching roles to missing parts and no per-parameter meaning beyond that.

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 verb 'Entscheide'/'Match' and the resource (roles of the original Saros 10R accessory set) are present, but 'welche unterschiedlichen Rollen des Original-Sets ... benötigt werden' is ambiguous (Rollen could read as roles or rollers) and the description never states what the tool actually returns as its decision. It does not distinguish itself from nearby parts-ordering siblings such as ersatzbestellung_nach_fund_aenderungsbedarf.

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?

'bei vorhandenen brauchbaren Ersatzteilen' and 'a confirmed Saros 10R kit' give an implied precondition for use, keyed to the modell_bestaetigt flag. There is no explicit when-not guidance and no alternative tool is named for the case where the kit or parts are not confirmed.

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