Skip to main content
Glama

getecoback-raumklima

philips_signaltoene_bedienfeld_ein_aus_start_ausnahme

Read-only

Prüft, ob Philips-2200-Bedienfeldtöne abschaltbar sind und welche Ein/Aus- und Start/Stopp-Signale erhalten bleiben — Check whether the available panel mute covers a specific sound requirement.

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>",
      "geraeusch": "<geraeusch>",
      "menue_nach_anleitung_geprueft": "<menue_nach_anleitung_geprueft>"
    },
    "name": "philips_signaltoene_bedienfeld_ein_aus_start_ausnahme"
  }
}

Input Schema

NameRequiredDescriptionDefault
modellYesVollständig gelesene Philips-Modellkennung.
geraeuschYesZu prüfendes Signal oder Geräusch.
menue_nach_anleitung_geprueftYesDie passende Bedienfeld-Einstellung wurde am exakten Modell nachgelesen und eindeutig geprüft.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false, so safety and locality are covered. The description adds that the tool verifies signal retention rather than just mutability, which is useful, but it never explains what the verdict looks like or how "offen" / ambiguous cases are surfaced — notable because there is no output schema.

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?

The core constraint is front-loaded in a single German sentence, but the bilingual duplication is not a true translation — the English clause compresses and slightly shifts the meaning, so it adds words without adding precision. The structure is acceptable but not tight.

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 three-parameter, read-only lookup with full schema coverage and no output schema, the description covers the subject of the check but not its result semantics. An agent knows what the tool examines, yet not what constitutes a positive, negative, or indeterminate 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 description coverage is 100% with enumerated values, so the parameters are already fully self-documenting. The description merely echoes the ein_aus_signal / start_stopp_signal enum concepts and adds no format or selection guidance beyond the schema, which is the baseline 3 case.

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 German sentence gives a concrete verb ("Prüft") plus two specific objects of the check: whether panel tones are mutable and which Ein/Aus and Start/Stopp signals are retained. The English gloss is looser ("covers a specific sound requirement") and slightly blurs the scope, but the overall purpose remains identifiable without opening the schema.

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 scenario is only implied: it is a check tied to a specific sound requirement and model, and the required boolean menue_nach_anleitung_geprueft hints at a precondition. There is no explicit when-to-use, when-not-to-use, or routing to any alternative — the agent must infer the call context.

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