Skip to main content
Glama

getecoback-raumklima

kaffeevollautomat_milchsystem_lattego_dampf_oder_tasse

Read-only

Vergleicht bei exakten Vollautomaten LatteGo, klassische Dampfdüse und Milch direkt in der Tasse mit deiner gewünschten Milch-Arbeitsfolge — Match a real milk workflow to the household requirement.

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>",
      "ziel": "<ziel>"
    },
    "name": "kaffeevollautomat_milchsystem_lattego_dampf_oder_tasse"
  }
}

Input Schema

NameRequiredDescriptionDefault
zielYesWelche Arbeitsfolge wird benötigt?
modellYesVollständiges Modell für den deutschen Markt.

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?

Annotations already establish that this is a read-only, closed-world operation. The description adds useful scope by saying the comparison is limited to exact fully automatic models and specific milk workflows, but it does not describe the comparison result, matching logic, or any limitations around the 'offen'/'anderes_modell' values.

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 description is compact and front-loads the comparison operation. The bilingual duplication is somewhat redundant, but it remains efficient and contains no clearly wasted explanatory text.

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, two-parameter comparison tool with a fully documented schema, the definition is adequate to support invocation. However, because there is no output schema, the description should ideally say more about what the comparison returns or how a match is represented.

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 both parameters have descriptive enum documentation. The description adds domain context by naming LatteGo, classic steam wand, and milk directly in the cup, but it does not explain how those map to the enum values or clarify the 'modell' choices beyond 'exakten Vollautomaten'.

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 gives a specific verb and resource: it compares LatteGo, classic steam wand, and milk-in-cup workflows against the desired milk workflow for exact fully automatic machines. The purpose is clear, though it does not explicitly differentiate itself from sibling tools beyond the milk-system focus.

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 implied by 'mit deiner gewünschten Milch-Arbeitsfolge' and 'Match a real milk workflow to the household requirement,' which suggests using the tool to match a household need to a milk workflow. There is no explicit when-to-use/when-not-to-use guidance and no named alternative 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