Skip to main content
Glama

getecoback-raumklima

philips_vorgemahlener_entkoffeinierter_kaffee_einzeltasse

Read-only

Prüft einen entkoffeinierten Einzelkaffee mit vorgemahlenem Kaffee neben dem Bohnenvorrat und ob zwei Tassen oder speichern dafür möglich sind — Check a decaf pre-ground serving without substituting the bean hopper.

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>",
      "bedarf": "<bedarf>"
    },
    "name": "philips_vorgemahlener_entkoffeinierter_kaffee_einzeltasse"
  }
}

Input Schema

NameRequiredDescriptionDefault
bedarfYesGewünschter Ablauf für den vorgemahlenen Kaffee.
modellYesAm Gerät eindeutig gelesene Philips-2200-Variante.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.8/5.0
Behavior3/5

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

Annotations declare readOnlyHint=true and openWorldHint=false, so the safety profile is already carried structurally. The description adds one genuinely useful behavioral fact — the bean hopper is not replaced/substituted by this operation — but says nothing about what the check returns, what happens on failure, or whether a 'remember for later' choice has any persistent effect (which the bedarf enum implies it might).

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?

Two compact clauses covering the same content in German and English with no padding, and the key constraint is front-loaded. The bilingual duplication and the opaque phrase "neben dem Bohnenvorrat" cost a little clarity but there is no wasted sentence.

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?

For a mandatory-two-parameter check tool with no output schema, the description should say what the check establishes and how the two enum choices change the outcome. Instead it leaves the core question ambiguous — whether this verifies feasibility, reports device state, or triggers an action — so an agent cannot confidently predict the result of a call.

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% with both parameters enum-constrained and documented, so the baseline is 3. The description loosely maps to the bedarf options ("zwei Tassen oder speichern") but adds no meaning about modell values or about what 'automatisch_fuer_spaeter_merken' actually commits the device to.

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?

Names a specific subject (a decaf pre-ground single serving) and a specific constraint (without substituting the bean hopper), but the operative verb is the vague "Prüft" / "Check" — it is never stated what is checked against what, or what result the agent gets back. An agent can tell it is about decaf pre-ground coffee but not clearly how it differs in effect from neighbouring Philips troubleshooting tools.

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 when-to-use, when-not-to-use, or prerequisite guidance is given; the phrase "neben dem Bohnenvorrat" hints at an alternative path (bean hopper vs. pre-ground) but never says when to pick this tool over that route. No sibling is named or excluded, and the agent must infer the trigger condition from the title alone.

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