Skip to main content
Glama

getecoback-raumklima

philips_azur_tropfstopp_eigene_beobachtung

Read-only

Beim DST7040/80 das Tropfstopp-Merkmal vom selbst beobachteten Ursprung eines einzelnen Tropfens trennen — Log observed droplet origin independently of the Drip Stop feature.

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_80_belegt": "<dst7040_80_belegt>",
      "beobachtet": "<beobachtet>",
      "gleicher_durchlauf": "<gleicher_durchlauf>"
    },
    "name": "philips_azur_tropfstopp_eigene_beobachtung"
  }
}

Input Schema

NameRequiredDescriptionDefault
beobachtetYesDirekt beobachteter Ursprung.
dst7040_80_belegtYesIst die vollständige /80 Variante für das beobachtete Gerät bestätigt?
gleicher_durchlaufYesIst der Beobachtung der tatsächlich identifizierte Durchlauf eindeutig zugeordnet?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.7/5.0
Behavior2/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 covered. The description adds only a conceptual distinction; it says nothing about what the tool does with the observation, whether unknown enum values ("offen") produce a valid result, or what the separated record looks like. The verb "log" is mildly at odds with a read-only profile, though "trennen" suggests analytic structuring rather than persistence.

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?

One bilingual sentence pair, front-loaded with the device model and the subject of the operation, with no filler. The German/English duplication costs a little space but aids disambiguation. Nothing is buried or padded.

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?

With only three fully documented parameters and annotations covering the safety profile, the definition is workable, but it omits what a caller gets back and what the "separation" produces — the central question for a tool whose whole purpose is distinguishing two things. Given no output schema exists, the description should carry that burden and does not.

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% and all three parameters are documented in the schema with enums spelled out, so the description need not repeat them. It does gesture at the semantic link between "beobachtet" and separating off the Drip Stop feature, which is slight added value. No format, precedence, or interaction rules (e.g. how "gleicher_durchlauf"=false should be interpreted) are supplied beyond the schema.

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 description names a device (DST7040/80) and a specific act — separating the Drip Stop feature from a directly observed droplet origin — which is more specific than a restatement of the name. However, "trennen"/"log ... independently" leaves unclear whether the tool stores a record, returns a structured comparison, or just validates inputs, so an agent cannot fully predict the outcome. Nothing in the text distinguishes it from the many sibling "..._beobachtung" documentation tools beyond the device and the drip-stop subject.

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 statement of when this tool should be invoked, when it should not, or which sibling to use instead for related observations (e.g. the drip-tray water tool or the sole-care evidence tool). The only implicit condition is the DST7040/80 device family, encoded in the name and required parameter rather than in prose. An agent must infer the triggering situation entirely.

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