Skip to main content
Glama

getecoback-raumklima

kaffeevollautomat_doppeltasse_zwei_kaffees_zwei_milchgetraenke

Read-only

Unterscheidet Doppeltaste für Kaffee und gleichzeitige Ausgabe von zwei Milchgetränken bei exakt belegten Modellen — Verify whether a double-cup mode covers coffee or two milk drinks.

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>",
      "ausgabe": "<ausgabe>"
    },
    "name": "kaffeevollautomat_doppeltasse_zwei_kaffees_zwei_milchgetraenke"
  }
}

Input Schema

NameRequiredDescriptionDefault
modellYesGenaue Modellkennung.
ausgabeYesGewünschte Ausgabe in einem Bedienablauf.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/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 safety is covered. The description adds the relevant behavioral nuance that answers are limited to exactly documented models, which goes slightly beyond annotations. It does not say what the response contains or how 'offen'/'anderes_modell' 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.

Conciseness3/5

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

A single sentence, but it is stated twice, once in German and once in English ('Verify whether a double-cup mode covers coffee or two milk drinks'), which largely repeats the tool name and the first clause. Front-loading is fine, but the bilingual redundancy costs space without new information.

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 two-parameter, read-only lookup with a fully described enum schema and no output schema, the description covers the core question adequately. It leaves the interpretation of the 'offen' fallback values and any notion of what a positive vs negative result means unaddressed.

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% with enumerated values for both parameters (modell and ausgabe), so the schema fully documents inputs. The description adds nothing about parameter meaning — notably it does not explain the 'offen' option in either enum — so it sits at the baseline.

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 concrete subject: whether the double button yields two coffees or two milk drinks, and scopes it to 'exakt belegten Modellen'. That is a specific verification task an agent can recognize. It stops short of differentiating from siblings such as kaffeevollautomat_milchsystem_lattego_dampf_oder_tasse, which touch adjacent milk-system questions.

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?

The phrase 'bei exakt belegten Modellen' signals the applicability boundary (only exactly documented models), which is useful context. However, it never states when to prefer this tool over the sibling milk-system or cleaning tools, nor what to do for 'anderes_modell'/'offen' values — the usage is only implied.

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