Skip to main content
Glama

getecoback-climate-weather

philips_na352_sync_spaetere_anzeigen_weitergabe

Read-only

Nach einer anfänglichen Synchronisationsanzeige den zuletzt belegten gemeinsamen Zeitstand für die Küchenübergabe bestimmen — Preserve separate evidence when only one programmed end time changed.

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": {
      "gleiche_sitzung_verfolgt": "<gleiche_sitzung_verfolgt>",
      "letzter_gemeinsamer_stand": "<letzter_gemeinsamer_stand>",
      "gross_endanzeige": "<gross_endanzeige>",
      "klein_endanzeige": "<klein_endanzeige>",
      "lage_nach_aenderung": "<lage_nach_aenderung>"
    },
    "name": "philips_na352_sync_spaetere_anzeigen_weitergabe"
  }
}

Input Schema

NameRequiredDescriptionDefault
gross_endanzeigeYesIst die neueste Endanzeige am großen Korb separat erneut abgelesen?
klein_endanzeigeYesIst die neueste Endanzeige am kleinen Korb separat erneut abgelesen?
lage_nach_aenderungYesTatsächliche beobachtete Beziehung der neuesten Endanzeigen.
gleiche_sitzung_verfolgtYesGehören Anfangs- und spätere Anzeigen derselben NA352/00-Sitzung an?
letzter_gemeinsamer_standYesWaren anfangs beide angezeigten Endzeiten tatsächlich zusammen dokumentiert?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.8/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 does not contradict this, since 'bestimmen' is a read/evaluate action. It adds genuine context beyond annotations by explaining that separate evidence should be preserved when only one end time changed, which signals the tool's evidentiary, non-mutating reasoning purpose. It stops short of saying what is returned or how conflicting evidence is resolved.

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?

It is short, two-clause, and the condition is placed after the main verb phrase, which is reasonable front-loading. But the German sentence is syntactically tangled and the English addendum mixes languages, making the core purpose harder to parse than necessary. Nothing is padded, yet clarity suffers.

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 five-required-parameter, read-only evaluation tool with no output schema, the description conveys the intent and one key behavioral nuance. It does not explain how the five evidence flags combine into a conclusion or what the caller receives, which matters here because the parameters are all evidence attestations. Adequate but with visible gaps.

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 five parameters carry enum or boolean descriptions, so the schema does the heavy lifting. The description's mention of 'separate evidence' and 'only one programmed end time changed' loosely maps to the gross/klein display parameters and the relationship parameter, but adds no new semantics about their interpretation. Baseline 3 applies.

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 an action ('bestimmen') and an object ('den zuletzt belegten gemeinsamen Zeitstand') tied to an initial sync indication, so the general shape of the operation is visible. However, the phrasing is dense domain jargon ('Küchenübergabe') and does not clearly separate this tool from the many sibling NA352 sync/observation tools. An agent would need to guess among several near-identical names.

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 statement of when to use this tool versus alternatives, nor any exclusions or prerequisites. The trailing clause 'Preserve separate evidence when only one programmed end time changed' is the only conditional hint, and it describes a behavior rather than when to select this tool. No sibling is named as an alternative.

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