Skip to main content
Glama

getecoback-raumklima

messluecken_ereignisgruppen_verdecken

Read-only

Prüfen, ob einzelne Lücken ein ganzes Ereignis verdecken, obwohl das Protokoll insgesamt dicht ist — Distinguish total missing time from the longest blind spot.

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": {
      "fenster_s": "<fenster_s>",
      "alle_luecken_s": "<alle_luecken_s>",
      "laengste_luecke_s": "<laengste_luecke_s>",
      "kuerzestes_ereignis_s": "<kuerzestes_ereignis_s>"
    },
    "name": "messluecken_ereignisgruppen_verdecken"
  }
}

Input Schema

NameRequiredDescriptionDefault
fenster_sYesDauer des Zielzeitraums, Sekunden.
alle_luecken_sYesSumme überschneidungsfreier unbeobachteter Zeitfenster.
laengste_luecke_sYesDauer der längsten einzelnen unbeobachteten Zeitspanne.
kuerzestes_ereignis_sYesKürzeste Dauer des gesuchten Ereignisses, 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 establish readOnlyHint=true and openWorldHint=false, so safety and side-effect questions are settled. The description adds useful semantics — that the check weighs whether individual gaps could swallow a whole event while overall coverage is dense — but it omits the decision rule (presumably comparing Summe/Längste Lücke against kuerzestes_ereignis_s) and the shape of the result. With annotations carrying the behavioral burden, a 3 is warranted.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The German clause is front-loaded and earns its place, but the English second clause largely restates the same intent in different words rather than adding new information. The bilingual duplication makes it longer than necessary for a single-purpose check.

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 four-required-number computation with no output schema, the description should say what a caller receives back (a boolean verdict, a threshold comparison result) and how the parameters combine. It frames the question well but stops short of describing the answer, leaving a meaningful gap for an agent that must interpret the call.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so units and bounds are already documented. The description earns extra credit by explicitly contrasting "total missing time" with "the longest blind spot", which disambiguates the two easily confused parameters alle_luecken_s and laengste_luecke_s that the schema alone presents side by side without relational context.

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?

States a specific check ("Prüfen, ob einzelne Lücken ein ganzes Ereignis verdecken") plus the qualifier "obwohl das Protokoll insgesamt dicht ist", which tells the agent this is about detecting concealment rather than raw gap counting. The purpose is clear, though it never says what form the verdict takes (boolean, label, list of gaps). No sibling differentiation, but the sibling list offers no plausible alternative for this computation.

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 condition of applicability is implied by the phrasing (gaps vs. minimum event duration), so an agent can infer when the tool is relevant. There is no explicit when-to-use vs when-not-to-use statement and no mention of alternatives or prerequisites, leaving guidance at the implied level.

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