Skip to main content
Glama

getecoback-raumklima

philips_azur_autoabschaltung_ruhelage_dokumentwert

Read-only

Für den bestätigten DST7040 die dokumentierten Auto-Abschaltzeiten auf Sohle und Standfläche unterscheiden — Read the specified idle threshold for the two documented resting positions.

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": {
      "dst7040_belegt": "<dst7040_belegt>",
      "position": "<position>",
      "ruhe_sekunden": "<ruhe_sekunden>"
    },
    "name": "philips_azur_autoabschaltung_ruhelage_dokumentwert"
  }
}

Input Schema

NameRequiredDescriptionDefault
positionYesWährend der gesamten Beobachtung bestätigte Ruhelage.
ruhe_sekundenYesEigene beobachtete Zeit ohne Benutzung in dieser Position.
dst7040_belegtYesIst der eigene DST7040 von der gelesenen Anleitung erfasst?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.7/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 genuine scope context: the value is a documented one from a manual, applies only to a confirmed DST7040, and is differentiated across the sole and standing-surface resting positions. It does not disclose what is returned or how the 'wechselnd_oder_offen' case 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?

The definition is short, but the German and English halves largely restate each other, with the English version adding no information. The most important qualifier (documented value for a confirmed DST7040) is present but the bilingual duplication dilutes front-loading.

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?

There is no output schema, so the description carries the burden of explaining the return value, and it never does: an agent cannot tell whether it receives a documented seconds figure per position, a comparison verdict, or an 'unknown' when dst7040_belegt is false. For a tool whose whole point is a 'Dokumentwert' lookup plus user observation, this missing half is a significant gap.

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%, including a documented enum for position, so the schema carries the parameter documentation burden. The description reinforces the two documented positions (Sohle, Standfläche) but says nothing about the third enum value 'wechselnd_oder_offen', the observed 'ruhe_sekunden', or the 'dst7040_belegt' gating flag. Baseline 3 is appropriate.

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 German sentence names a specific resource (dokumentierte Auto-Abschaltzeiten) constrained to two resting positions for a confirmed DST7040, which is more than a restatement of the name. However, the English half ('Read the specified idle threshold') is vague and partly redundant, and neither half states whether the tool returns the documented value or compares it against the supplied observation. An agent can guess the domain but not the exact operation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use or when-not-to-use guidance and no pointer to any sibling, despite several sibling tools covering related Azur observations (e.g. the Beobachtung/Schrittgrenze and Pflegeaussage tools). The phrase 'Für den bestätigten DST7040' implies a precondition but never states what to do when the device is not confirmed or when the position is undetermined.

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