Skip to main content
Glama

getecoback-raumklima

philips_abtropfschale_wasser_spuelwasser_oder_aussen

Read-only

Unterscheidet bei einem Philips-Vollautomaten Wasser in der Abtropfschale nach beobachtetem Spülen von Wasser außerhalb oder ohne bekannten Zyklus — Scope an observed water location to a documented rinse, without diagnosing a leak.

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>",
      "wasserort": "<wasserort>",
      "spuelvorgang": "<spuelvorgang>"
    },
    "name": "philips_abtropfschale_wasser_spuelwasser_oder_aussen"
  }
}

Input Schema

NameRequiredDescriptionDefault
modellYesExaktes Philips-2200-Modell.
wasserortYesSicher beobachteter Ort ohne Öffnen von Gehäusen.
spuelvorgangYesEin Spülvorgang wurde im gleichen Beobachtungsabschnitt direkt festgestellt.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true and openWorldHint=false, so the agent knows this is a closed-world read-only operation. The description adds behavioral scope: it is a classification/scoping tool, not a leak diagnosis. It does not describe what the scoping result looks like or any output behavior, but with annotations covering safety, a 3 is appropriate.

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?

The core purpose is front-loaded in the German clause, and the English clause reinforces the scope boundary. The bilingual repetition is slightly redundant but not wasteful; every sentence contributes to understanding. It is appropriately sized.

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 simple read-only classification tool with three enum parameters, the description covers purpose and scope adequately. It does not explain what the tool returns (there is no output schema), and it omits usage alternatives, leaving some contextual gaps.

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 all three parameters documented and enum-constrained. The description adds no parameter-level meaning beyond the schema, so the baseline of 3 applies.

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 specific verb and resource: it differentiates/classifies water in a Philips coffee machine drip tray according to whether rinse was observed versus water outside or without known cycle. The English clause 'Scope an observed water location to a documented rinse, without diagnosing a leak' sharpens the purpose. It does not explicitly differentiate itself from any sibling tool, which keeps it from a 5.

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?

Implicit guidance exists: use this to scope observed water to a documented rinse and explicitly not to diagnose a leak. However, there is no explicit when-to-use trigger, no named alternative, and no statement of prerequisites beyond the observed facts.

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