Skip to main content
Glama

getecoback-raumklima

philips_perfectcare_statusleuchte_wasser_vs_entkalkung

Read-only

Bei PSG7140/70 eine eindeutig erkannte Wassertankanzeige oder Entkalkungserinnerung dem passenden Dokumentabschnitt zuordnen — Identify the next documentation section by the confirmed indicator.

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": {
      "psg7140_70_belegt": "<psg7140_70_belegt>",
      "anzeige": "<anzeige>"
    },
    "name": "philips_perfectcare_statusleuchte_wasser_vs_entkalkung"
  }
}

Input Schema

NameRequiredDescriptionDefault
anzeigeYesAnhand Text, Symbollegende oder Bedienungsanleitung eindeutig erkannte Anzeige.
psg7140_70_belegtYesGenau PSG7140/70 anhand der Gerätekennung bestätigt?

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?

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is known. The description adds that the tool maps a confirmed indicator to a documentation section, but it does not explain how ambiguous enum cases like 'beide' or 'nur_leuchten_gesehen' are handled. It adds some context but leaves meaningful behavioral gaps.

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 description is short and front-loads the PSG7140/70 condition. The German sentence is followed by an English restatement that mostly repeats the same idea, which adds mild redundancy but does not obscure the definition. It is efficient overall.

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?

The tool is low-complexity and its two parameters are fully described in the schema, with read-only annotations covering safety. However, there is no output schema, and the description does not specify the return format or how ambiguous indicator states are resolved. It is adequate but not complete.

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 both parameters are already documented in the schema. The description references confirmed water-tank or descaling indicators, which loosely maps to the 'anzeige' parameter, but it adds no extra meaning for 'beide', 'nur_leuchten_gesehen', or 'psg7140_70_belegt'. Baseline 3 is appropriate.

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 states a specific verb and resource: assigning a recognized water-tank indicator or descaling reminder to the matching documentation section for PSG7140/70. It names the exact model and indicator types, so an agent can tell what the tool does. It does not explicitly differentiate itself from similarly named sibling tools, which keeps it below 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?

The description gives an implied condition for use: only when the indicator has been clearly recognized and the device is PSG7140/70. It does not state when not to use the tool or name an alternative for ambiguous or unconfirmed cases. That makes the guidance adequate but incomplete.

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