Skip to main content
Glama

getecoback-climate-weather

miele_wwr880_cap_restwasser_nach_programmende

Read-only

Kleine Wassermenge in der Miele Cap nach dokumentiertem Programmende einordnen — Distinguish the described residual water from proof that the whole cap dose was delivered.

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": {
      "modellbeleg": "<modellbeleg>",
      "programmende": "<programmende>",
      "beobachtung": "<beobachtung>"
    },
    "name": "miele_wwr880_cap_restwasser_nach_programmende"
  }
}

Input Schema

NameRequiredDescriptionDefault
beobachtungYesWas wurde unmittelbar danach an der benutzten Cap beobachtet?
modellbelegYesSind WWR 880 WPS und die am eigenen Gerät einschlägige deutsche Anleitung M.-Nr. 11 767 692 bestätigt?
programmendeYesIst das Programmende am Gerät unabhängig vom Aussehen der Cap bestätigt?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/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 genuinely useful epistemic context beyond that: small residual water must be distinguished from evidence of full dose delivery, which tells the agent this is an interpretive/reasoning tool rather than a measurement or lookup.

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?

A single front-loaded German sentence followed by a short English gloss; nothing is wasted and the key constraint comes first. The bilingual restatement is mildly duplicative but aids clarity for an opaque German-titled tool.

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

Completeness4/5

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

For a three-parameter, read-only interpretation tool with a fully documented schema and no output schema, the description supplies enough framing to call it correctly. Minor gap: it does not describe what form the assessment result takes, though that is a small omission given the tool's nature.

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 all three parameters carry descriptive enum values, so the schema already does the heavy lifting. The description's mention of 'dokumentiertem Programmende' loosely maps to the programmende parameter but adds no new semantics for modellbeleg or beobachtung; 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 action (einordnen/classify a small amount of residual water in the Miele Cap) tied to a specific condition (documented program end), and explicitly contrasts that observation with proof that the full cap dose was delivered. The verb+resource is clear, though siblings are not named, so differentiation relies on the conceptual framing rather than routing.

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?

Usage context is implied by 'nach dokumentiertem Programmende' plus the enum values, which make clear this is an interpretation step after a confirmed cycle end. There is no explicit statement of when not to use it or which sibling to prefer for other residual-water or dosing questions.

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