Skip to main content
Glama

getecoback-raumklima

miele_g7673_powerdisk_auto_oder_manuell

Read-only

Beim Miele G 7673 den Dosiervorgang nach bestätigtem AutoDos- und PowerDisk-Zustand zuordnen — Resolve the active detergent path before adding anything.

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>",
      "autodos": "<autodos>",
      "disk": "<disk>"
    },
    "name": "miele_g7673_powerdisk_auto_oder_manuell"
  }
}

Input Schema

NameRequiredDescriptionDefault
diskYesBestätigter Disk-Zustand für diese Entscheidung.
autodosYesTatsächlich bestätigter AutoDos-Zustand.
anleitung_bestaetigtYesGenaue deutsche Modellkennung und genannte Anleitung am konkreten Gerät abgeglichen?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/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 safety profile is covered. The description adds the precondition of confirmed AutoDos/PowerDisk states and the timing before adding detergent, but it does not explain the resolution logic, the returned path, or how 'offen' states are handled.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two compact clauses, front-loaded with the model and action. The bilingual restatement is functional rather than redundant, and there is no unnecessary wording.

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?

With no output schema, the description should clarify what 'Resolve the active detergent path' returns, such as an AutoDos-versus-manual recommendation, and how 'offen' inputs affect the result. It is adequate for purpose and preconditions but incomplete for a decision 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 coverage is 100%, and all three parameters are documented, including two enums. The description reinforces that AutoDos and PowerDisk states must be confirmed, but it adds no new meaning for 'anleitung_bestaetigt' or for the individual enum values, so the baseline of 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?

States a specific action and resource: 'Dosiervorgang ... zuordnen' and 'Resolve the active detergent path' for the Miele G 7673. It is clear enough to separate this from generic appliance tools, but it does not name a sibling or explain how it differs from related AutoDos tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a clear trigger: use after the AutoDos and PowerDisk states are confirmed, and before adding anything. It does not explicitly say when not to use it or name an alternative sibling tool.

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