Skip to main content
Glama

getecoback-raumklima

messlogger_raster_phasen_gleichzeit

Read-only

Ermitteln, ob zwei regelmäßig getaktete Logger bei festem Zeitversatz je exakt gleichzeitig erfassen — Check whether fixed periodic logs have any exact timestamp coincidences.

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": {
      "raster_a_s": "<raster_a_s>",
      "raster_b_s": "<raster_b_s>",
      "erster_versatz_s": "<erster_versatz_s>"
    },
    "name": "messlogger_raster_phasen_gleichzeit"
  }
}

Input Schema

NameRequiredDescriptionDefault
raster_a_sYesPeriodendauer des ersten Loggers in ganzen Sekunden.
raster_b_sYesPeriodendauer des zweiten Loggers in ganzen Sekunden.
erster_versatz_sYesAbstand der ersten geplanten Stichproben in ganzen 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 agent knows this is a side-effect-free, closed-world computation; the description correctly adds nothing that contradicts that. It does not say whether the result is a simple yes/no, a count, or the actual coinciding timestamps, and there is no output schema to fill that gap, which keeps it at a middling score.

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 compact clauses, front-loaded with the German statement and followed by an English gloss that adds the term 'timestamp coincidences'. The bilingual duplication is mildly redundant but short enough not to waste space.

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 three-required-parameter pure computation with no output schema, the definition covers the inputs but leaves the return value and edge-case behavior (zero offset, identical periods, no coincidence) unspecified. Annotations carry the safety profile, so this is adequate but not complete.

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 parameter carries its own German explanation with units (seconds) and bounds, so the schema already does the semantic work. The description only restates 'regelmäßig getaktet' and 'festem Zeitversatz' without adding interpretation such as what a zero offset or coprime periods imply.

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 (determine whether two periodically sampled loggers ever sample at exactly the same instant) plus the qualifying condition (fixed time offset), which is enough for an agent to distinguish it from a plain duplicate-analysis tool. It does not, however, contrast itself with the sibling messlogger_raster_dubletten_auswertbar, so the differentiation is only implicit.

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 implied by the phrasing 'check whether ... coincidences' — an agent can infer this is the tool for a collision/coincidence question — but there is no explicit when-to-use, when-not-to-use, or pointer to an alternative for related raster questions.

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