Skip to main content
Glama

getecoback-raumklima

philips_milch_kaffee_getraenkemenge_groesste_stufe_speichern

Read-only

Prüft beim Philips 2200, welche Getränkemenge dauerhaft gespeichert werden kann und wann ein separates Milchmengenfeld belegt ist — Check which volume setting can be saved for a specific beverage.

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>",
      "groessenstufe": "<groessenstufe>",
      "getraenk": "<getraenk>"
    },
    "name": "philips_milch_kaffee_getraenkemenge_groesste_stufe_speichern"
  }
}

Input Schema

NameRequiredDescriptionDefault
modellYesGenaue Modellkennung.
getraenkYesAm konkreten Modell belegtes Preset.
groessenstufeYesGewünschte Stufe aus dem Getränkemengenmenü.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.5/5.0
Behavior2/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 needed to explain the result of the check (what a positive/negative answer looks like, how the milk quantity field interacts) and does not. It also does not clarify whether the tool merely verifies or actually persists anything, despite "speichern" in the name.

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 bilingual with partial redundancy and the German half carries the only real content. It is front-loaded reasonably but the model-specific "Philips 2200" phrase is wasted or misleading space.

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

Completeness2/5

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

There is no output schema, so the description carries the burden of explaining what the check returns, and it does not. For a conditional query tool whose whole purpose is to produce a yes/no about a milk quantity field, that is a substantial gap.

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 enums on all three parameters, so the baseline is 3. The description adds the notion that the result depends on model and beverage and mentions the milk quantity field, but also says "Philips 2200", which is narrower than the model enum (EP2231/40, EP2220/10, anderes_modell, offen) and may mislead.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Prüft ... welche Getränkemenge dauerhaft gespeichert werden kann" gives a verb plus resource, but the description narrows the scope to "Philips 2200" while the name and schema cover a save/volume-level operation across multiple models, so the actual subject of the check is muddled. The added clause about the milk quantity field helps slightly but is not enough to make it crisply distinguishable from the many sibling Philips checks.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No statement of when to call this versus another tool, no prerequisites, and no exclusion criteria. An agent must infer from the name alone that this is a pre-check before persisting a volume level.

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