Skip to main content
Glama

getecoback-raumklima

bosch_air4000i_fernfunktion_quellen_schnitt

Read-only

Entscheide, ob eine App-Funktionsangabe für das angebotene Bosch-Air-Modell überhaupt zugeordnet ist — Determine whether a Bosch Air app feature is documented for the offered variant

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": {
      "geraet": "<geraet>",
      "quellenvariante": "<quellenvariante>",
      "app_funktion_explizit": "<app_funktion_explizit>",
      "angebot_kennung_geprueft": "<angebot_kennung_geprueft>"
    },
    "name": "bosch_air4000i_fernfunktion_quellen_schnitt"
  }
}

Input Schema

NameRequiredDescriptionDefault
geraetYesVollständige Produktidentifikation
quellenvarianteYesModell auf der Fundstelle zur App-Funktion
app_funktion_explizitYesGenau die vorgesehene Funktion wird beschrieben, nicht nur ein App-Logo
angebot_kennung_geprueftYesModellkennung im Angebot ist vollständig geprüft

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.6/5.0
Behavior2/5

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

Annotations declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered and the bar is lower. The description adds nothing beyond that: it does not say what the tool returns (a verdict? a boolean?), how the four inputs are combined, or whether conflicting variants cause a rejection. 'Entscheide' only weakly implies a decision output.

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 a single front-loaded sentence, which is good, but it is essentially duplicated in German and English without the English half adding precision — the two halves even diverge in meaning. No waste beyond that, but no extra structure either.

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 four required enum parameters, no output schema, and a gate-check role, the description should at minimum state the decision outcome and how the variant fields interact. It conveys the topic but not the return semantics or the rejection condition, though the fully-described schema partly compensates.

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% and three parameters carry enums with their own descriptions, so the schema does the heavy lifting and baseline 3 applies. The description hints at the core comparison (offered variant vs. source variant) but does not clarify the crucial distinction between 'geraet' and 'quellenvariante' or the meaning of the 'offen' values.

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 description does name a decision verb and the resource ('whether a Bosch Air app feature is documented for the offered variant'), which is more than a restatement of the cryptic tool name. However, the German 'zugeordnet' (assigned/attributable) and the English gloss 'documented' do not mean the same thing, leaving the actual verdict criterion ambiguous. There is no differentiation from the many sibling Bosch/appliance 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 Guidelines2/5

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

No when-to-use, when-not-to-use, or alternative is stated. The agent must infer from the required parameters that this is a pre-citation gate check before attributing an app feature to a device. Nothing says what to do when a parameter is 'offen'.

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