Skip to main content
Glama

getecoback-raumklima

kaffeevollautomat_bruehgruppe_reinigungsroutine_modellwechsel

Read-only

Vergleicht beim Wechsel der Kaffeemaschine, ob die vorhandene wöchentliche oder monatliche Reinigung der Brühgruppe beide Modellvorgaben erfüllt — Compare brew-group care cadence after switching an exact model.

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": {
      "zielmodell": "<zielmodell>",
      "wasserpflege": "<wasserpflege>",
      "monatliche_fettloesung": "<monatliche_fettloesung>"
    },
    "name": "kaffeevollautomat_bruehgruppe_reinigungsroutine_modellwechsel"
  }
}

Input Schema

NameRequiredDescriptionDefault
zielmodellYesGenaue Kennung des Modells, für das die Routine geplant wird.
wasserpflegeYesEingeplante Häufigkeit für diesen tatsächlich gepflegten Teil.
monatliche_fettloesungYesMonatliche Pflege mit der für das Zielmodell ausdrücklich ausgewiesenen Kaffeefettlöser-Tablette ist für diese Brühgruppe eingeplant.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

The readOnlyHint=true and openWorldHint=false annotations match the comparison-only wording and already establish safety and closed-world behavior. Beyond that, the description says the check covers both model specifications but does not explain the result shape, how 'offen' values are handled, or other behavioral details.

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 comparison action and model-switch context. The immediate German-English duplication repeats the same content rather than adding structure, which costs a point but does not obscure the tool.

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?

The description gives enough to understand the input scenario and the three dimensions being compared, but with no output schema it leaves the return or decision format unspecified. Treatment of 'offen' and 'anderes_modell' is also unaddressed, which is a meaningful gap for a comparison 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% and all three enum parameters are documented, so the schema carries the detailed parameter semantics. The description contextualizes 'wasserpflege' as existing weekly or monthly cleaning and 'zielmodell' as the switched model, but adds no format, decision logic, or edge-case meaning beyond 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 states a specific verb and resource: it compares the brew group's existing weekly or monthly cleaning routine against model requirements when switching machines. The scope is narrow enough to distinguish this from general coffee-machine maintenance, though it does not explicitly contrast itself with related sibling 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?

The usage context is clear: this is for a model switch, when the existing brew-group cleaning cadence must be checked against both model requirements. It does not state when not to use the tool or name alternatives for adjacent maintenance tasks, so it stops short of full routing guidance.

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