Skip to main content
Glama

getecoback-raumklima

kaffeevollautomat_automatikspuelung_milchsystem_pflegebeleg

Read-only

Prüft, ob ein automatischer Spülvorgang und die gesonderte Reinigung benutzter Milchteile jeweils belegt sind — Distinguish a machine rinse from documented cleaning of removable milk components.

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>",
      "milchsystem_benutzt": "<milchsystem_benutzt>",
      "spuelung_beobachtet": "<spuelung_beobachtet>",
      "milchteile_gereinigt": "<milchteile_gereinigt>"
    },
    "name": "kaffeevollautomat_automatikspuelung_milchsystem_pflegebeleg"
  }
}

Input Schema

NameRequiredDescriptionDefault
modellYesVollständige Modellkennung.
milchsystem_benutztYesBenutzung der Milchkomponenten in diesem Durchlauf ist belegt oder ausgeschlossen.
spuelung_beobachtetYesDer automatische Spülvorgang wurde direkt beobachtet.
milchteile_gereinigtYesDie dafür vorgesehenen Milchkomponenten wurden separat entsprechend der Modellunterlage gepflegt.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/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 and the description is consistent with it ("Prüft" is a pure check). It adds the useful behavioral nuance that two separate evidence facts are being assessed and must not be conflated. It does not say what the check returns or how an "offen" value is treated, which is the main remaining gap.

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 sentence states the check first and the disambiguation second, with no filler. The bilingual German/English mix is slightly awkward but the English clause is the most information-dense part and is placed where it is read.

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?

For a read-only, four-required-enum verification tool the description covers what is being checked and why the two facts differ. With no output schema, however, it should indicate what a result looks like (a combined verdict, per-aspect status, or a conflict flag), and it gives no hint about how the "offen" enum values affect the outcome.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with four enum parameters, so the baseline is 3; the description earns an extra point because it explains the conceptual difference between spuelung_beobachtet (directly observed machine rinse) and milchteile_gereinigt (separately documented care of removable parts), which is exactly the distinction an agent could otherwise blur. It still adds nothing about the modell or milchsystem_benutzt parameters, but those are self-explanatory in the schema.

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 verb ("Prüft") and a specific object of verification: whether an automatic rinse and a separate cleaning of used milk parts are each documented. The added clause sharpens the distinction between a machine rinse and documented cleaning of removable milk components, so the tool is clearly identifiable. It does not, however, contrast itself with any of the many sibling kaffeevollautomat tools, so it stops short of full sibling differentiation.

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 is only implied: the wording makes clear this is an evidence/verification check rather than an action, and the rinse-vs-cleaning distinction hints at when the two evidence types matter. There is no explicit "use this when…" statement, no exclusion of alternatives, and no mention of prerequisites such as which model documentation must be on hand.

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