Skip to main content
Glama

getecoback-climate-weather

kurzgeraeusch_abtastluecke_im_pegelprotokoll

Read-only

Prüft, ob ein beobachteter kurzer Klang vollständig zwischen zwei Einzelablesungen liegen kann — Check whether a recorded brief sound could fall wholly between instantaneous samples.

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": {
      "ereignis_ms": "<ereignis_ms>",
      "abstand_ms": "<abstand_ms>",
      "punktabtastung_belegt": "<punktabtastung_belegt>"
    },
    "name": "kurzgeraeusch_abtastluecke_im_pegelprotokoll"
  }
}

Input Schema

NameRequiredDescriptionDefault
abstand_msYesDokumentierter gleichmäßiger Abstand zwischen Einzelablesungen in ms.
ereignis_msYesDauer des kurzen Geräuschs aus einer feineren vorhandenen Aufzeichnung in ms.
punktabtastung_belegtYesSind die vorhandenen Ausgabewerte periodische Momentaufnahmen ohne Intervallmittel oder Spitzenhaltung?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare this is a read-only, closed-world operation, so the safety bar is low. The description adds that the result is a possibility judgement ('könnte ... liegen') rather than a measurement, which is valuable framing, but it says nothing about how the verdict is expressed or what boundary conditions (e.g. exactly equal to abstand_ms) mean.

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?

It is short and front-loaded, but the German sentence and the English sentence carry the same information, so roughly half the text is redundant duplication. Every sentence earns its place only once the other language is discounted.

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?

This is a simple read-only computation with fully documented parameters, so little is required. However, with no output schema present, the definition should signal what the caller gets back (a yes/no verdict? a margin?) and it does not, leaving a real gap for an agent deciding how to use the result.

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 three parameters are already documented, which sets the baseline at 3. The description reinforces the relationship between the event duration and the sampling interval but adds no units, formats, or edge-case meaning beyond what the schema already provides.

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 states a specific check: whether a recorded brief sound can lie wholly between two instantaneous readings. The verb ('Prüft') and the resource/condition (short sound vs. sampling interval) are concrete enough that an agent knows this is a feasibility/aliasing test, not a measurement tool. It does not distinguish itself from any sibling by name, 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?

Usage is implied rather than stated: the scenario (observed brief sound, known uniform sampling interval, confirmed instantaneous sampling) is embedded in the wording, but there is no explicit when-to-use, when-not-to-use, or named alternative among the many similarly named siblings. An agent must infer the preconditions itself.

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