Skip to main content
Glama

getecoback-raumklima

philips_perfectcare_bereitlicht_nachfuellanzeige_protokoll

Read-only

Für eine passende deutsche 7000er Anleitung die Bereitschaftsanzeige nach einem Tankhinweis durch beobachtete Reihenfolge einordnen — Distinguish readiness from a water alert using recorded display order.

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": {
      "anleitung_am_geraet_bestaetigt": "<anleitung_am_geraet_bestaetigt>",
      "vorgang": "<vorgang>",
      "bereitschaft": "<bereitschaft>"
    },
    "name": "philips_perfectcare_bereitlicht_nachfuellanzeige_protokoll"
  }
}

Input Schema

NameRequiredDescriptionDefault
vorgangYesVerlauf in demselben beobachteten Vorgang.
bereitschaftYesTatsächlich beobachtete Bereitschaftsanzeige für diesen Vorgang.
anleitung_am_geraet_bestaetigtYesIst genau die verlinkte west-europäische Anleitung vom Hersteller oder anhand der Originalunterlagen dem eigenen Gerät 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 safety needs no restating. The description adds that the judgment rests on 'beobachtete Reihenfolge' (observed sequence) rather than inference, which is useful behavioral context, but it never says what the resulting classification is or how an ambiguous observation is handled.

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?

It is short, but the two sentences are near-duplicates across languages and the German sentence is convoluted and front-loads the confusing manual-matching frame before the actual action. Restating the same content in English costs space without adding routing information.

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?

This is a read-only classification tool with no output schema, so the description carries the burden of describing the verdict an agent will get back — and it never does. An agent knows the inputs but not what 'einordnen' returns, nor what the manual-confirmation gate does to the outcome.

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%, so the enums and the manual-confirmation boolean are already documented; baseline is 3. The description reinforces the tank-hint case and the observed-order basis, but says nothing about the most consequential parameter, anleitung_am_geraet_bestaetigt, whose gate semantics stay entirely in the schema.

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 English half states a recognizable operation: distinguish the readiness indicator from a water alert using recorded display order. But the leading German clause ('Für eine passende deutsche 7000er Anleitung ... einordnen') frames it as matching a German 7000-series manual, which muddies whether the tool classifies an observation or looks up documentation. It also gives no explicit hand-off against the close-sounding sibling philips_perfectcare_statusleuchte_wasser_vs_entkalkung.

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?

'nach einem Tankhinweis' implies the trigger condition: call this after a refill/tank alert is observed. The 'passende deutsche 7000er Anleitung' phrasing hints at a precondition (device must match that manual), but neither the precondition nor any when-not case is stated outright, and no alternative tool is named.

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