Skip to main content
Glama

getecoback-climate-weather

geraetemessung_originaldatei_teilzitat_abdeckung

Read-only

Prüfe, welchen Teil eines Originalzeitraums ein weitergereichter Messauszug belegt — Check how much of the original time span a forwarded measurement excerpt covers

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": {
      "original_start_min": "<original_start_min>",
      "original_ende_min": "<original_ende_min>",
      "auszug_start_min": "<auszug_start_min>",
      "auszug_ende_min": "<auszug_ende_min>",
      "identische_originalversion": "<identische_originalversion>"
    },
    "name": "geraetemessung_originaldatei_teilzitat_abdeckung"
  }
}

Input Schema

NameRequiredDescriptionDefault
auszug_ende_minYesLetzter Zeitstempel des Auszugs
auszug_start_minYesErster Zeitstempel des weitergegebenen Auszugs
original_ende_minYesEnde des ursprünglichen Protokolls ab gemeinsamer Zeitbasis
original_start_minYesBeginn des ursprünglichen Protokolls ab gemeinsamer Zeitbasis
identische_originalversionYesAuszug ist eindeutig demselben unveränderten Export zugeordnet

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, so the safety profile is covered and the description is consistent with it. Beyond that it only restates that this is a check; it does not say what is returned (a fraction, a boolean, a residual interval) or how non-identical versions are handled. Modest added context against a lower bar set by the annotations.

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 sentence with the object of the check front-loaded and no filler. The German/English duplication doubles the length with identical content, mildly wasteful, but it is plausibly there for cross-language matching and does not obscure the meaning.

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?

With five required numeric parameters, no output schema, and a gating boolean, the description should at least indicate the shape of the result and the effect of a false identische_originalversion. It establishes the comparison being performed but leaves the outcome contract entirely 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 all five parameters are already documented, including the identische_originalversion gate. The description adds the conceptual framing that the two timestamp pairs form an 'original time span' versus a 'forwarded excerpt', which clarifies intent but no syntax or edge-case semantics. 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 gives a concrete verb ('Prüfe') and a specific computed relation: how much of an original time span a forwarded measurement excerpt covers. An agent can tell this is an interval-coverage check rather than a lookup. It offers no differentiation from the many sibling '*_abdeckung' tools, which is the only reason it falls short of 5.

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 statement of when to use this tool, when not to, or which sibling handles a related coverage question. The closest thing to a precondition ('identische_originalversion') lives only in the schema, and the description never says what to do when that flag is false.

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