Skip to main content
Glama

getecoback-raumklima

messlogger_raster_dubletten_auswertbar

Read-only

Eindeutig belegte, doppelte und widersprüchliche Rasterzeiten in einem Messprotokoll getrennt zählen — Audit usable timestamp slots without mistaking duplicates for coverage.

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": {
      "soll_zeiten": "<soll_zeiten>",
      "zeilen_im_raster": "<zeilen_im_raster>",
      "unterschiedliche_zeiten": "<unterschiedliche_zeiten>",
      "widerspruch_zeiten": "<widerspruch_zeiten>",
      "zeilen_ausserhalb": "<zeilen_ausserhalb>"
    },
    "name": "messlogger_raster_dubletten_auswertbar"
  }
}

Input Schema

NameRequiredDescriptionDefault
soll_zeitenYesErwartete Rasterzeiten im abgegrenzten Protokoll.
zeilen_im_rasterYesZeilen mit passender Zeit einschließlich Wiederholungen.
zeilen_ausserhalbYesWeitere Zeilen außerhalb des vereinbarten Rasters.
widerspruch_zeitenYesVerschiedene Rasterzeiten mit inhaltlich widersprüchlichen Werten.
unterschiedliche_zeitenYesVerschiedene Rasterzeiten, für die mindestens eine Zeile vorliegt.

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 safety is covered. The description adds the non-obvious semantic point that duplicates must not be counted as coverage, which is genuinely useful. It says nothing about how the counting is derived or what the result looks like, which matters for an audit 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?

One front-loaded sentence plus a short English gloss; nothing is padded and the core verb-resource pair comes first. The bilingual restatement is slightly redundant but clarifies intent rather than wasting 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?

Five required parameters, no output schema, and a computation whose result semantics (e.g. how duplicates versus contradictions are separated) are only loosely implied. The description conveys the auditing intent but not enough detail for an agent to predict the output precisely.

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 coverage is 100%, so all five numeric inputs are already documented. The description echoes the three counting categories that map onto widerspruch_zeiten, unterschiedliche_zeiten and the coverage concept, but adds no new constraints or units beyond the schema. 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 action (counting separately) on a specific resource (Rasterzeiten in a Messprotokoll) and splits it into three named categories: uniquely covered, duplicate, and contradictory. That is far more specific than the tool name alone. It does not explicitly distinguish itself from the sibling messlogger_raster_phasen_gleichzeit, 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 clause 'Audit usable timestamp slots without mistaking duplicates for coverage' implies the use case (coverage auditing) and a pitfall to avoid. However, it never states when to prefer this tool over the related raster tools, nor any preconditions on the inputs.

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