Skip to main content
Glama

getecoback-climate-weather

philips_aquaclean_durchfluss_kaffeetassen_wechselintervall

Read-only

Prüft die 95 Liter durch den AquaClean-Filter und das Dreimonatsintervall ohne Getränkemenge als vollständige Filtermenge zu zählen — Check independently documented time and throughput for an AquaClean filter change.

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>",
      "filterwechsel_zugeordnet": "<filterwechsel_zugeordnet>",
      "monate_voll": "<monate_voll>",
      "menge": "<menge>",
      "liter": "<liter>"
    },
    "name": "philips_aquaclean_durchfluss_kaffeetassen_wechselintervall"
  }
}

Input Schema

NameRequiredDescriptionDefault
literYesGemessene Liter für die angegebene Erfassung.
mengeYesWelche Ausgänge sind in der angegebenen Menge erfasst?
modellYesExakte Philips-2200-Variante.
monate_vollYesVollendete Kalendermonate seit Einsetzen dieses Exemplars.
filterwechsel_zugeordnetYesEin bestätigtes AquaClean-Exemplar mit belegtem Beginn ist dieser Beobachtung zugeordnet.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/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 the safety profile is covered. The description adds real context beyond that: the check treats the 95-liter throughput and three-month interval as full filter volume when beverage quantity is not recorded, which explains the reasoning model behind the tool. It does not disclose the response shape or what happens when data is incomplete, so it stops short of full transparency.

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?

One sentence plus a short English gloss — compact and front-loaded on the check itself. But the German half is syntactically broken (an infinitive clause with no main verb), which costs comprehension relative to its length.

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?

Placeholder.

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 all five parameters are documented in the schema itself, making 3 the baseline. The description does reinforce the meaning of the 'menge' dimension (counting without beverage quantity as full volume), which is a small value-add on top of the enum documentation, but it adds nothing for modell, monate_voll, liter or filterwechsel_zugeordnet.

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?

The description names a specific subject (AquaClean filter's 95-liter / three-month change interval) and a verb ("Prüft" / "Check independently documented"), so the general purpose is inferable. However, the German clause is grammatically tangled and never states cleanly what the check returns or how it differs from the sibling AquaClean filter tools. It is a vague-but-not-tautological purpose.

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?

There is no explicit when-to-use or when-not-to-use statement, and no sibling is named as an alternative even though the catalog contains several AquaClean-related tools. The mention of "ohne Getränkemenge" hints at a scenario, but the agent must guess the boundary conditions for invoking this versus the other filter tools.

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