Skip to main content
Glama

getecoback-climate-weather

messprotokolle_zeitfenster_schneiden

Read-only

Überlappung zweier paralleler Messprotokolle für denselben Versuch bestimmen — Compute which part of two logs actually covers the same period.

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": {
      "a_start_min": "<a_start_min>",
      "a_ende_min": "<a_ende_min>",
      "b_start_min": "<b_start_min>",
      "b_ende_min": "<b_ende_min>"
    },
    "name": "messprotokolle_zeitfenster_schneiden"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_ende_minYesEnde von Protokoll A ab dem Nullpunkt, in Minuten.
b_ende_minYesEnde von Protokoll B ab dem Nullpunkt, in Minuten.
a_start_minYesBeginn von Protokoll A ab einem gemeinsamen Nullpunkt, in Minuten.
b_start_minYesBeginn von Protokoll B ab dem Nullpunkt, in Minuten.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior2/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. Beyond that the description adds almost nothing: it does not say whether a non-overlapping pair yields an empty result, a zero duration, or an error, nor what form the intersection is expressed in. For a pure computation tool this is a meaningful omission.

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?

One sentence, front-loaded with the core operation and followed by an English paraphrase that aids comprehension. The bilingual repetition is mild redundancy rather than padding, so it stays tight.

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

Completeness2/5

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

There is no output schema, so the description should explain what the tool returns (overlap start/end? duration? empty result?) and how boundary cases are handled. Neither is covered, leaving the agent unable to interpret the result of an otherwise simple four-parameter computation.

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%: all four minute-valued parameters (a_start_min, a_ende_min, b_start_min, b_ende_min) are documented in the schema with shared-zero-point semantics and 0–525600 bounds. The description adds no further meaning about the parameters, so the 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 (compute the overlap/intersection of two measurement-log time windows for the same experiment) with a concrete verb and resource, so an agent knows exactly what is being calculated. It does not differentiate itself from a similarly named sibling such as fassadenbeschattung_zeitfenster_ueberlappung, so it stops short of a 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 scenario is implied by 'zweier paralleler Messprotokolle für denselben Versuch', which tells the agent this is for two logs of one experiment. There is no explicit when-to-use/when-not statement, no named alternative, and no instruction about what to do if the windows do not overlap.

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