Skip to main content
Glama

getecoback-climate-weather

miele_g7673_solo_nach_multitab_mangelanzeige

Read-only

Bei einem Reinigerwechsel ausgeblendete Mangelanzeigen unabhängig vom Vorrat lesen — Identify the missing refill evidence when changing from a multi-function cleaner to solo detergent.

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": {
      "anleitung_bestaetigt": "<anleitung_bestaetigt>",
      "wechsel": "<wechsel>",
      "mangelanzeige": "<mangelanzeige>"
    },
    "name": "miele_g7673_solo_nach_multitab_mangelanzeige"
  }
}

Input Schema

NameRequiredDescriptionDefault
wechselYesBelegter Wechsel beim konkreten Gerät.
mangelanzeigeYesBekannter Anzeigezustand.
anleitung_bestaetigtYesGenaue deutsche Modellkennung und genannte Anleitung am konkreten Gerät abgeglichen?

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?

The annotations already establish that this is a read-only, closed-world operation. The description adds one useful behavioral nuance: it reads hidden indicators independently of current stock, which is not captured by annotations. It does not describe the return format or any other operational constraints beyond that.

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-loads the operational condition before the purpose. The German sentence is followed by an English translation, which adds some length, but neither version is verbose or unstructured.

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?

There is no output schema, and the description does not explain what evidence or result the tool returns. The input schema is fully documented and annotations cover safety, but an agent still lacks return-value context for a read-only evidence-retrieval 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 the three parameters are already documented in the input schema. The description reinforces the 'Wechsel' and 'ausgeblendete' concepts but adds no extra meaning for the required 'anleitung_bestaetigt' confirmation flag. Baseline 3 applies when the schema carries the parameter semantics.

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 concrete verb ('lesen'/'Identify') and a specific resource ('ausgeblendete Mangelanzeigen'/'missing refill evidence') scoped to a cleaner change. It is distinguishable from related salt or AutoDos tools because it names the multi-function-to-solo transition, though the wording remains somewhat opaque.

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 phrase 'Bei einem Reinigerwechsel' implies the usage context, and 'unabhängig vom Vorrat' clarifies the condition under which the tool applies. However, it gives no explicit when-not-to-use guidance and does not name an alternative sibling tool for adjacent scenarios.

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