Skip to main content
Glama

getecoback-raumklima

philips_azur_spray_dampfart_beobachtung_zuordnen

Read-only

Beim DST7040 Wasserspray, vertikalen Dampfstoß und fortlaufenden Dampf nach beobachtetem Bedienelement unterscheiden — Attribute an observed spray or steam event to its confirmed control and position.

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>",
      "bedienelement": "<bedienelement>",
      "lage": "<lage>"
    },
    "name": "philips_azur_spray_dampfart_beobachtung_zuordnen"
  }
}

Input Schema

NameRequiredDescriptionDefault
lageYesBeobachtete Lage beim Vorgang.
bedienelementYesBestätigt beobachtete Eingabe.
dst7040_belegtYesIst DST7040 im Gerätehandbuch zugeordnet?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already state readOnlyHint=true and openWorldHint=false, so safety and locality are covered, and the description does not contradict them (zuordnen is a read-only assignment). The description adds that the input must be a *confirmed* observation and that distinguishing spray vs. steam types is the core operation. It says nothing about what is returned (a label? a record?), which would matter for a tool with 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 content is front-loaded and only one sentence long, but the German clause and the English clause largely restate each other, so roughly half the text is duplication. The dense noun stacking ('DST7040 Wasserspray, vertikalen Dampfstoß und fortlaufenden Dampf') is hard to parse without the schema enums.

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, all-required classification tool there is no output schema, so the description should indicate what the assignment yields; it does not. Annotations cover the read-only profile, and the enum fields clarify the input space, leaving the tool adequately but not fully specified.

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 two enum-typed parameters whose descriptions already explain 'Beobachtete Lage' and 'Bestätigt beobachtete Eingabe'. The description mentions Bedienelement and Lage and the DST7040 constraint, but adds no format, phrasing, or cross-parameter rules beyond the schema. Baseline 3 is appropriate when the schema does the heavy lifting.

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 verb+resource: attribute an observed spray/steam event to its confirmed control and position, and it enumerates the event types (DST7040 water spray, vertical steam burst, continuous steam). An agent can tell this is a classification/assignment tool rather than a measurement tool. It stops short of naming which sibling to pick instead, so it is not 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 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 alternative tool is named. The only usage signal is implicit in the phrase 'unterscheiden … nach beobachtetem Bedienelement', which hints at classifying an observation but leaves the agent to infer preconditions and boundaries against the long list of sibling observation tools.

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