Skip to main content
Glama

getecoback-climate-weather

miele_guard_l1_abluftanzeige_reset_vor_wechsel

Read-only

Prüfe nach einem bestätigten Wechsel, ob der aktuelle Anzeigezustand zum beschriebenen Zurücksetzen am Guard L1 passt — Decide whether the documented appliance reminder reset has its preconditions

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": {
      "hs22_bestaetigt": "<hs22_bestaetigt>",
      "geraeteanzeige_leuchtet": "<geraeteanzeige_leuchtet>",
      "abluftfilter_gewechselt": "<abluftfilter_gewechselt>",
      "nur_filterstreifen_erfasst": "<nur_filterstreifen_erfasst>"
    },
    "name": "miele_guard_l1_abluftanzeige_reset_vor_wechsel"
  }
}

Input Schema

NameRequiredDescriptionDefault
hs22_bestaetigtYesDeutsche Guard L1 Ausführung mit Typ HS22 und zugeordneter Anleitung M.-Nr. 13 114 040 bestätigt
abluftfilter_gewechseltYesPassender Abluftfilter wurde in diesem Vorgang tatsächlich ausgetauscht
geraeteanzeige_leuchtetYesAbluftfilter-Wechselanzeige am Gerät leuchtet jetzt eindeutig
nur_filterstreifen_erfasstYesBeleg betrifft die Anzeige am Ersatzfilter statt am Gerät

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

readOnlyHint=true and openWorldHint=false already tell the agent this is a closed-world read/decision, so the bar is lower. The description adds the sequencing context (only after a confirmed change) but says nothing about what the outcome means — e.g. whether a negative verdict implies the reset must be deferred — and there is no output schema to fall back on.

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 single sentence is short but awkwardly built: the German and English halves restate the same idea rather than front-loading the purpose, and the em-dash construction buries the actual decision being made. Nothing is extraneous in length, but the phrasing costs clarity.

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 decision tool with no output schema, the description should say what a positive versus negative judgement means and what the agent should do next. It establishes the input situation but not the result semantics, leaving a real gap for callers.

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 four parameters, including the two enum-typed ones, are fully explained in the schema. The description adds only an indirect hint that a confirmed change and the on-device indicator state matter, which is already covered. Baseline 3 applies.

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 and judgement ('Prüfe ... ob ... passt' / 'Decide whether') on a specific resource: the Abluftfilter-Wechselanzeige reset on a Guard L1 with HS22 documentation. It is clear that this is a precondition check rather than the reset itself, though the German clause is convoluted enough that it takes a second read to confirm that no mutation occurs. It offers no explicit differentiation from the many similar Miele Guard L1 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?

'nach einem bestätigten Wechsel' gives one piece of timing guidance — consult this after a change has been confirmed. There is no statement of when not to use it, no prerequisite ordering, and no named alternative for the case where the change is not yet confirmed or where the indicator is off.

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