Skip to main content
Glama

getecoback-raumklima

miele_quickpowerwash_autoopen_zehnminuten_geltungsfall

Read-only

Die Herstellerangabe zur möglichen AutoOpen-Verzögerung nur auf den nachgewiesenen QuickPowerWash-Fall beziehen — Restrict the ten-minute support note to its documented branch.

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": {
      "herstellerfall_zugeordnet": "<herstellerfall_zugeordnet>",
      "quickpowerwash_belegt": "<quickpowerwash_belegt>",
      "ende_autoopen_gelesen": "<ende_autoopen_gelesen>",
      "keine_manuelle_oeffnung_oder_aus": "<keine_manuelle_oeffnung_oder_aus>",
      "automatisches_oeffnen_beobachtet": "<automatisches_oeffnen_beobachtet>"
    },
    "name": "miele_quickpowerwash_autoopen_zehnminuten_geltungsfall"
  }
}

Input Schema

NameRequiredDescriptionDefault
ende_autoopen_gelesenYesDie Anzeige Ende/AutoOpen wurde am Programmende abgelesen.
quickpowerwash_belegtYesDas gewählte Programm war dokumentiert QuickPowerWash.
herstellerfall_zugeordnetYesIst der Miele-Unterstützungshinweis genau diesem Modell und Funktionsstand zugeordnet?
automatisches_oeffnen_beobachtetYesEine automatische Türbewegung wurde tatsächlich beobachtet.
keine_manuelle_oeffnung_oder_ausYesDas Gerät blieb bis zum Ende der Beobachtung ohne manuelles Öffnen oder Ausschalten.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.8/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is clear and the description does not contradict it. The description adds the scoping rule being enforced, but it does not explain the outcome, failure behavior, or what happens if required conditions are 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?

The definition is short and front-loaded, with the scoping rule stated immediately. The bilingual repetition is somewhat redundant, but it does not obscure the core statement.

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 five-parameter validation-like tool with no output schema, so the description should clarify what invoking it returns or how the boolean inputs combine. Instead it only states the restriction being applied, leaving the agent without enough information 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 description coverage is 100%, and each of the five required booleans is documented in the input schema. The description adds no parameter-level meaning beyond the schema, so the baseline score of 3 is appropriate.

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 identifies a specific subject: restricting the ten-minute AutoOpen support note to the documented QuickPowerWash case. However, it does not say what operation the tool performs—validate, record, or return an applicability result—and it does not distinguish itself from sibling tools beyond its narrow topic.

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?

It states the substantive condition 'only on the documented QuickPowerWash case' but gives no guidance on when an agent should call this tool versus alternatives. No exclusions, prerequisites, or sibling alternatives are named.

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