Skip to main content
Glama

getecoback-raumklima

philips_na352_sync_versetzter_beginn_beobachtung

Read-only

Zeitversetzte programmierte Starts bei beobachtetem gemeinsamen Ende protokollieren — Separate observed start offset from the claim of a synchronized finish.

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": {
      "start_ende_desselben_laufs": "<start_ende_desselben_laufs>",
      "gross_start_min": "<gross_start_min>",
      "klein_start_min": "<klein_start_min>",
      "gross_ende_min": "<gross_ende_min>",
      "klein_ende_min": "<klein_ende_min>",
      "genauigkeit_min": "<genauigkeit_min>"
    },
    "name": "philips_na352_sync_versetzter_beginn_beobachtung"
  }
}

Input Schema

NameRequiredDescriptionDefault
gross_ende_minYesBeobachtete Programmendeminute des großen Korbs.
klein_ende_minYesEntsprechendes Ende des kleinen Korbs.
genauigkeit_minYesGemeinsame Beobachtungstoleranz für Start- und Endabstände.
gross_start_minYesTatsächlich beobachtete Programmstartminute des großen Korbs.
klein_start_minYesEntsprechender Start des kleinen Korbs.
start_ende_desselben_laufsYesSind alle vier angezeigten Ereignisse am exakt bestätigten NA352/00 derselben Sitzung zugeordnet?

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 the safety profile is covered. The description adds the observed-offset-versus-claim distinction but does not explain return behavior or what happens when the required same-session boolean is false.

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 one front-loaded sentence with no filler, and the English clause adds a meaningful distinction rather than merely repeating the German. The mixed-language phrasing is slightly cryptic but not verbose.

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 six required parameters, no output schema, and fully described schema fields, the definition is sufficient to invoke the tool. It still lacks explicit sibling routing and any explanation of how mismatches or the boolean confirmation affect the result.

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?

All six parameters have schema descriptions at 100% coverage, so the schema carries most parameter meaning. The description groups them as observed start/end offsets and a synchronized-finish claim, but adds no format or validation detail beyond the schema.

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 German verb 'protokollieren' and object 'zeitversetzte programmierte Starts' state a specific action, and the English clause narrows it to separating observed offsets from a synchronized-finish claim. It does not explicitly name a sibling alternative, so it stops short of 5.

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 condition 'bei beobachtetem gemeinsamen Ende' implies when to use the tool, but there is no explicit when-not guidance or named alternative sibling. An agent must infer that this is for offset starts rather than ordinary sync observation.

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