Skip to main content
Glama

getecoback-raumklima

philips_perfectcare_bewegungssensor_automatik_beobachtung

Read-only

Bei der PSG7140/70 einen gemeldeten Dampfausstoß mit dokumentierter Automatik und tatsächlich beobachteter Bewegung einordnen — Attribute an event to automatic steam only when its trigger was observed.

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>",
      "automatik": "<automatik>",
      "ausloeser": "<ausloeser>"
    },
    "name": "philips_perfectcare_bewegungssensor_automatik_beobachtung"
  }
}

Input Schema

NameRequiredDescriptionDefault
ausloeserYesFür den fraglichen Dampfausstoß konkret beobachteter Auslöser.
automatikYesWar der Automatikbezug laut Anzeige oder dem bestätigten Handbuch eindeutig geklärt?
psg7140_70_belegtYesIst der Code PSG7140/70 belegt?

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 safety is covered. The description adds a meaningful classification rule about observed triggers, but does not describe return behavior, handling of unmet conditions, or other operational details.

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 definition is compact and front-loads the device context. The bilingual restatement is mildly redundant but not bloated, and the core instruction is easy to locate.

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 low-complexity, read-only classification tool with fully documented parameters and no output schema, the description is adequate. It still leaves the return semantics and alternative-tool routing implicit.

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 three parameters are already well documented in the input schema. The description echoes automatik and observed Bewegung but adds little parameter-level meaning beyond what the schema provides.

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 action (einordnen/attribute), a specific phenomenon (gemeldeter Dampfausstoß), and a specific device code (PSG7140/70). This makes the tool identifiable against the many sibling observation tools, though it does not explicitly name an alternative.

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?

It gives one clear usage condition: attribute an event to automatic steam only when its trigger was observed. It does not explain when to use this tool instead of another observation tool, nor what to do when the trigger was not observed.

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