Skip to main content
Glama

getecoback-climate-weather

philips_kaffeesatzbehaelter_leer_anzeige_bleibt_zaehler

Read-only

Prüft beim leeren Kaffeesatzbehälter mit weiter leuchtender Anzeige, ob er bei ausgeschalteter Philips-Kaffeemaschine geleert wurde — Separate a stale grounds-counter signal from the observed contents.

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>",
      "behaelter_jetzt_leer": "<behaelter_jetzt_leer>",
      "leeranzeige_bleibt": "<leeranzeige_bleibt>",
      "zustand_beim_leeren": "<zustand_beim_leeren>"
    },
    "name": "philips_kaffeesatzbehaelter_leer_anzeige_bleibt_zaehler"
  }
}

Input Schema

NameRequiredDescriptionDefault
modellYesAbgelesene Philips-2200-Variante.
leeranzeige_bleibtYesDie eindeutig identifizierte Aufforderung zum Leeren bleibt sichtbar.
zustand_beim_leerenYesBeobachteter Einschaltzustand während des Leerens.
behaelter_jetzt_leerYesDer tatsächliche Kaffeesatzbehälter wurde als leer festgestellt.

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?

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds diagnostic framing about decoupling a stale counter from observed contents, but says nothing about what the result looks like or how the verdict is expressed.

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 tight clauses with the condition front-loaded followed by a clarifying English gloss. No filler; the bilingual repetition is justified for disambiguation.

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

Completeness4/5

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

For a read-only, four-enum observation check with no output schema, the description supplies the scenario an agent needs to decide to call it. Only the shape of the returned verdict is left implicit.

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%, so the four enums are already documented. The description adds some relational meaning, tying 'weiter leuchtender Anzeige' to the display flag and 'ausgeschalteter Maschine' to the power-state parameter, but does not deepen the enum semantics beyond that.

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?

States a specific verb ('Prüft') and resource (Kaffeesatzbehälter with a still-lit display), and the clause 'Separate a stale grounds-counter signal from the observed contents' pins down the diagnostic intent. It does not name a sibling to contrast with, so an agent cannot fully rule out overlapping tools from the description alone.

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 triggering context is explicit: use when the grounds container is empty but the display remains lit. There is no explicit when-not guidance or named alternative, so it stops short of a 5.

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