Skip to main content
Glama

getecoback-climate-weather

sensorprotokoll_uhrdrift_abgleichen

Read-only

Zwei Uhrabgleiche für einen Messlogger nutzen und einen Zeitversatz interpolieren — Align a sensor timestamp using two reference clock checks.

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": {
      "dauer_min": "<dauer_min>",
      "ereignis_min": "<ereignis_min>",
      "versatz_anfang_s": "<versatz_anfang_s>",
      "versatz_ende_s": "<versatz_ende_s>"
    },
    "name": "sensorprotokoll_uhrdrift_abgleichen"
  }
}

Input Schema

NameRequiredDescriptionDefault
dauer_minYesMinuten zwischen den beiden Uhrabgleichen, auf der Referenzuhr.
ereignis_minYesGrobe Lage des Ereignisses nach dem ersten Abgleich, in Minuten auf der Referenzuhr.
versatz_ende_sYesLoggerzeit minus Referenzzeit beim zweiten Abgleich, in Sekunden.
versatz_anfang_sYesLoggerzeit minus Referenzzeit beim ersten Abgleich, in Sekunden.

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 that the offset is interpolated between two checks, which tells the agent the result is a computed, deterministic value rather than a lookup, but it says nothing about behavior for out-of-range offsets, whether drift is assumed linear, or what the caller receives back.

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?

A single front-loaded sentence covering method and outcome, with a parallel English rendering for disambiguation. The bilingual duplication is mild redundancy but stays short and wastes no space on filler.

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 pure computation tool with fully documented parameters and clear annotations, most of what an agent needs is present. The notable gap is that no output schema exists and the description never says what is returned (an aligned timestamp, an applied offset, both), which leaves the agent guessing about the result shape.

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 each of the four parameters is documented in the schema with units and sign convention (logger time minus reference time). The description only echoes the two-check structure, so it adds no meaning beyond the schema; baseline 3 is appropriate.

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 operation on a specific object: interpolating a time offset and aligning a sensor timestamp for a measurement logger using two reference clock checks. That distinguishes it from the other 'abgleichen' siblings, which deal with appliances, tariffs, or labels rather than logger clock drift. It is clear without needing the schema, though it never states the deliverable (a corrected timestamp) explicitly.

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 precondition is implied rather than stated: the agent can infer it needs two clock checks bracketing the event. There is no explicit when-to-use vs. when-not guidance and no named alternative for the single-check case, so an agent must reason about applicability from the method description alone.

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