Skip to main content
Glama

getecoback-raumklima

miele_guard_app_registrierung_gegen_wechselmeldung

Read-only

Unterscheide die Anzeige passenden Zubehörs nach Registrierung von einer aktiven Wechselmeldung beim belegten L1 Comfort — Check whether app registration actually proves a connected replacement notification

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": "<modell>",
      "registrierung_beobachtet": "<registrierung_beobachtet>",
      "vernetzung_bestaetigt": "<vernetzung_bestaetigt>",
      "gesuchter_beleg": "<gesuchter_beleg>"
    },
    "name": "miele_guard_app_registrierung_gegen_wechselmeldung"
  }
}

Input Schema

NameRequiredDescriptionDefault
modellYesVollständig erfasste Guard-Variante
gesuchter_belegYesWas möchte ich unterscheiden
vernetzung_bestaetigtYesAktive Verbindung genau dieses Geräts war protokolliert
registrierung_beobachtetYesDas passende Gerät ist mit seiner Modellkennung im Profil erfasst

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.7/5.0
Behavior2/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. Beyond that the description adds only the 'belegter L1 Comfort' context; it says nothing about how the four enum inputs are weighed, what the outcome looks like, or what happens when inputs conflict or are 'offen' — and with no output schema, that gap is the description's responsibility.

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 short and the core distinction is front-loaded, but the English clause largely restates the German clause instead of adding information, and the two halves are joined by an em dash in a way that reads as two competing descriptions rather than one.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a four-input adjudication tool with no output schema, so the description must explain the decision logic and the shape of the answer. It explains neither, leaving the agent unable to know what a 'ja/nein/offen' combination produces or how to interpret the result.

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 every parameter carries an enum with an explanatory German description, so the schema does the heavy lifting. The description adds no interpretation of what combinations of 'registrierung_beobachtet', 'vernetzung_bestaetigt' and 'gesuchter_beleg' mean for the discrimination, so baseline 3 applies.

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 names a specific subject (display of matching accessories after registration vs. an active replacement notification on the occupied L1 Comfort) and a discernible verb ('Unterscheide' / 'Check whether'). But it never states what the tool actually returns — a verdict, a boolean, a diagnosis — and the bilingual doubling makes the one-sentence purpose harder to pin down than it needs to be.

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?

The task framing implies when the tool applies (you are unsure whether a registration observation proves a real replacement notification), but there is no explicit when-not, no prerequisites, and no reference to any sibling tool. Guidance is inferable rather than stated.

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