Skip to main content
Glama

getecoback-climate-weather

geraeuschwiederholung_abstandsregelmaessigkeit

Read-only

Prüft aus vier beobachteten Einsätzen, wie stark die Abstände wiederkehrender Geräusche schwanken — Check variation between four observed sound onsets.

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": {
      "erster_sek": "<erster_sek>",
      "zweiter_sek": "<zweiter_sek>",
      "dritter_sek": "<dritter_sek>",
      "vierter_sek": "<vierter_sek>",
      "spannungsgrenze_sek": "<spannungsgrenze_sek>"
    },
    "name": "geraeuschwiederholung_abstandsregelmaessigkeit"
  }
}

Input Schema

NameRequiredDescriptionDefault
erster_sekYesErster beobachteter Einsatz in Sekunden.
dritter_sekYesDritter beobachteter Einsatz in Sekunden.
vierter_sekYesVierter beobachteter Einsatz in Sekunden.
zweiter_sekYesZweiter beobachteter Einsatz in Sekunden.
spannungsgrenze_sekYesEigene maximale Abweichung zwischen längstem und kürzestem Abstand in Sekunden.

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 agent knows this is a safe, self-contained computation. The description adds that the result concerns the scatter of intervals across four onsets, but says nothing about the role of spannungsgrenze_sek as a tolerance threshold or what form the answer takes (a verdict vs. a spread value), which matters since there is 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?

A single front-loaded sentence with the operative verb first, plus a short bilingual gloss. Nothing is wasted, though the German/English duplication adds little for a reader who already reads the parameter names.

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 five-required-parameter computation with no output schema and no annotations about return values, the description should say what the tool reports back and how spannungsgrenze_sek affects that answer. It covers what is measured but leaves the agent guessing about the result shape.

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 every parameter, including spannungsgrenze_sek, is already documented as a bounded seconds value. The description's 'vier beobachteten Einsätzen' merely restates the four onset parameters and adds no interpretation of the units, ordering, or threshold semantics.

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?

Names a specific operation ('Prüft ... wie stark die Abstände ... schwanken') on a specific input domain (four observed sound onsets), and the English gloss confirms the reading. It does not differentiate itself from any sibling, but the purpose itself is unambiguous.

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 this check is appropriate, what precondition must hold (e.g. that the four onsets are already identified as the same recurring sound), or what alternative to use instead. The agent must infer usage entirely from the name and the parameter names.

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