Skip to main content
Glama

getecoback-raumklima

geraet_geraeuschlog_zwei_uhranker_abgleichen

Read-only

Rechnet eine Geräuschmarke mit zwei gemeinsamen Zeitankern auf das Betriebsprotokoll um — Align a recorded sound marker to an appliance log using two shared time anchors.

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": {
      "audio_start": "<audio_start>",
      "audio_ende": "<audio_ende>",
      "log_start": "<log_start>",
      "log_ende": "<log_ende>",
      "audio_spitze": "<audio_spitze>"
    },
    "name": "geraet_geraeuschlog_zwei_uhranker_abgleichen"
  }
}

Input Schema

NameRequiredDescriptionDefault
log_endeYesZweiter Anker auf der Betriebsuhr in Sekunden.
log_startYesErster Anker auf der Betriebsuhr in Sekunden.
audio_endeYesZweiter gemeinsamer Anker auf der Audio-Uhr in Sekunden.
audio_startYesErster gemeinsamer Zeitanker auf der Audio-Uhr in Sekunden.
audio_spitzeYesZeitstempel des beobachteten Geräuschereignisses auf der Audio-Uhr in Sekunden.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/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's 'umrechnen/align' framing is consistent with a pure computation. It does not, however, disclose what the transformation returns (a single converted timestamp? an offset?), nor whether out-of-range or non-monotonic anchors are rejected, which matters for a tool with no output schema.

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 with the operation and its inputs, presented bilingually. The German/English duplication is slightly redundant but adds no filler or hedging.

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 computation with no output schema, the description should at least indicate the shape of the result and what happens when the two clocks cannot be reconciled. Annotations cover the safety profile, but the return value remains entirely unspecified.

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 every parameter is documented in the schema, so the baseline is 3. The description adds only the framing that the anchors are 'shared' between the audio and appliance clocks; it contributes nothing about units, ordering constraints, or what audio_spitze means relative to the anchor pair beyond what the schema already states.

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 concrete operation (convert/align) applied to two named resources (sound marker, appliance log) with a stated method (two shared time anchors). It is far more specific than a title restatement, though it never names a sibling such as sensorprotokoll_uhrdrift_abgleichen or geraeuschereignis_sel_und_zeitfenster_abgleichen to disambiguate the family of 'abgleichen' tools.

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 when-to-use or when-not-to-use guidance, no prerequisites, and no named alternative. The agent must infer from the wording that this is the right tool only when exactly two common anchors exist between the audio clock and the appliance clock.

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