Skip to main content
Glama

getecoback-raumklima

philips_na352_copy_status_gegen_sync_verwechseln

Read-only

Bei einer Werbeaussage über denselben Zeitplan COPY und synchronisiertes Ende auseinanderhalten — Separate identical programmed settings from the scheduling function.

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_belegt": "<modell_belegt>",
      "beobachtete_funktion": "<beobachtete_funktion>",
      "dauer_gleich_gezeigt": "<dauer_gleich_gezeigt>",
      "temperatur_gleich_gezeigt": "<temperatur_gleich_gezeigt>",
      "ende_gleich_behauptet": "<ende_gleich_behauptet>"
    },
    "name": "philips_na352_copy_status_gegen_sync_verwechseln"
  }
}

Input Schema

NameRequiredDescriptionDefault
modell_belegtYesExakte deutsche NA352/00-Ausführung belegt.
beobachtete_funktionYesIm dokumentierten Lauf verwendete Funktion.
dauer_gleich_gezeigtYesWar dieselbe anfängliche Programmdauer an beiden Anzeigen tatsächlich sichtbar?
ende_gleich_behauptetYesWird nur ein gleichzeitiges Ende als Beleg für gleiche Einstellungen angeführt?
temperatur_gleich_gezeigtYesWar derselbe eingestellte Temperaturwert tatsächlich sichtbar?

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 the analytic intent (separating identical programmed settings from the scheduling function) but says nothing about how the booleans combine into a verdict or what the caller receives, which is the behavior an agent most needs here.

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?

It is two short clauses with the condition front-loaded before the action. The German/English duplication is slightly redundant but does not obscure meaning.

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 read-only, closed-world adjudication tool with no output schema, the description should indicate what result is produced (e.g. a verdict or classification). It states the conceptual distinction but leaves the return value and decision logic implicit, which is a meaningful 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%, so every parameter is already documented with a German description, including the enum for observed function. The description adds no parameter-level nuance beyond the schema, so the baseline 3 applies.

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 the specific distinction it adjudicates – COPY versus a synchronized end for the same schedule – and frames it around a marketing claim. It is clear what the tool is for, though the phrasing is abstract and it does not contrast itself with the many sibling NA352 observation tools.

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 opening clause ('Bei einer Werbeaussage über denselben Zeitplan') implies a use context, so an agent can infer when it applies. There are no explicit when-not conditions and no named alternatives among the sibling tools covering adjacent sync observations.

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