Skip to main content
Glama

getecoback-climate-weather

miele_boost_cx1_fadenheber_oder_bodenduesenersatz

Read-only

Prüfe bei der dokumentierten Bodendüse, ob der sichtbare Verschleiß nur die separat vorgesehenen Fadenheber betrifft — Distinguish a worn replaceable lint strip from the nozzle itself

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": {
      "cx1_bestaetigt": "<cx1_bestaetigt>",
      "originale_duese_aus_abbildung": "<originale_duese_aus_abbildung>",
      "flor_am_fadenheber_verschlissen": "<flor_am_fadenheber_verschlissen>",
      "duese_anderswo_beschaedigt": "<duese_anderswo_beschaedigt>"
    },
    "name": "miele_boost_cx1_fadenheber_oder_bodenduesenersatz"
  }
}

Input Schema

NameRequiredDescriptionDefault
cx1_bestaetigtYesDeutsche Boost CX1 Cat & Dog PowerLine-Ausführung 11602420 und zugeordnete Anleitung bestätigt
duese_anderswo_beschaedigtYesAußerhalb des Fadenhebers liegt eine sichtbare Beschädigung der Düse vor
originale_duese_aus_abbildungYesDie vorliegende umschaltbare Bodendüse entspricht dem dokumentierten Typ mit Steckeinsätzen
flor_am_fadenheber_verschlissenYesFlor am Fadenheber sichtbar verschlissen

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 agent knows this is a safe, closed-world assessment. The description adds genuine domain context beyond that — that the lint strip is a separately available replaceable part, so a worn strip does not imply nozzle replacement — which shapes how the result should be interpreted. It does not disclose how the four inputs combine into a verdict, or what happens when cx1_bestaetigt is false.

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?

A single front-loaded sentence with an appended English gloss; nothing extraneous. The bilingual duplication is slightly redundant and the dash construction is a little awkward, but it costs little and widens comprehension.

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 four-required-parameter, fully documented read-only assessment with no output schema, inputs and safety profile are adequately covered. What is missing is any statement of the outcome — whether the tool returns a recommendation to replace the strip versus the nozzle, or merely records observations — which matters for a decision-oriented tool.

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 every parameter is already documented, including the three ja/nein/offen enums, and the baseline of 3 applies. The description does add framing value by positioning flor_am_fadenheber_verschlissen and duese_anderswo_beschaedigt as the two competing explanations, but it gives no additional enum-value semantics or tie-breaking rules.

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 verification task on a named resource: check whether the visible wear on the documented floor nozzle affects only the separately provided Fadenheber. The English gloss ('distinguish a worn replaceable lint strip from the nozzle itself') makes the discriminating purpose unambiguous even for a non-German reader. It stops short of naming a sibling, but the 'oder Bodenduesenersatz' framing in the name plus the explicit either/or in the text already separates it from the filter-mat and canister siblings.

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 implied rather than stated: the check applies 'bei der dokumentierten Bodendüse', which presupposes the confirmed-device precondition encoded in cx1_bestaetigt. There is no explicit when-to-use/when-not statement and no alternative tool named for the case where the nozzle is damaged elsewhere or the device is 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