Skip to main content
Glama

getecoback-raumklima

messdauer_zeitumstellung_korrigieren

Read-only

Echte Messdauer bei Umstellung von Sommer- und Winterzeit bestimmen — Correct elapsed time using recorded UTC offsets from both ends of a household measurement.

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": {
      "lokale_differenz_min": "<lokale_differenz_min>",
      "start_utc_offset_min": "<start_utc_offset_min>",
      "ende_utc_offset_min": "<ende_utc_offset_min>"
    },
    "name": "messdauer_zeitumstellung_korrigieren"
  }
}

Input Schema

NameRequiredDescriptionDefault
ende_utc_offset_minYesEnd-Zeitzonenversatz in Minuten, in Deutschland normalerweise 60 oder 120.
lokale_differenz_minYesDifferenz der notierten lokalen Zeitpunkte einschließlich Kalendertag, in Minuten.
start_utc_offset_minYesStart-Zeitzonenversatz in Minuten, in Deutschland normalerweise 60 oder 120.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/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, and the description is consistent with a pure calculation. It adds the useful behavioral detail that the correction is derived from the recorded UTC offsets at both ends, but says nothing about the result's form or the sign convention of the returned duration.

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?

Two short clauses, front-loaded with the core operation, with no filler. The German/English duplication costs a little space but aids clarity rather than obscuring it.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a three-required-parameter, side-effect-free calculation with full schema coverage and no output schema, the description supplies enough to call it correctly: what is computed and from which inputs. Only the output convention (units, sign) is left implicit.

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 each parameter (local minute difference, start and end UTC offsets) is already fully documented including ranges and typical German values. The description adds only the general framing that both ends' offsets are used, so 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 a specific operation (determining true elapsed measurement time) and its condition (the summer/winter time change), which an agent can distinguish from generic household-measurement siblings. The bilingual restatement is clear but slightly redundant, and no sibling is named as an alternative.

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?

Usage is only implied: the agent can infer this applies when a measurement spans a DST transition and both endpoints' UTC offsets were recorded. There is no explicit when-to-use/when-not guidance and no alternative tool is named for measurements that do not cross a clock change.

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