Skip to main content
Glama

getecoback-climate-weather

geraeuschereignisse_rate_je_beobachtungsstunde

Read-only

Vergleicht Häufigkeiten markierter Spitzen aus zwei verschieden langen aktiven Beobachtungen — Normalize recorded sound-event counts to an observation hour.

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": {
      "a_anzahl": "<a_anzahl>",
      "b_anzahl": "<b_anzahl>",
      "a_dauer_sek": "<a_dauer_sek>",
      "b_dauer_sek": "<b_dauer_sek>",
      "gleiche_zaehlweise": "<gleiche_zaehlweise>"
    },
    "name": "geraeuschereignisse_rate_je_beobachtungsstunde"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_anzahlYesGezählte Ereignisse in Block A.
b_anzahlYesGezählte Ereignisse in Block B.
a_dauer_sekYesBelegte Dauer von Block A in Sekunden.
b_dauer_sekYesBelegte Dauer von Block B in Sekunden.
gleiche_zaehlweiseYesGleiche Geräuschdefinition, Gerätephase und Beobachtungskriterien?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/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. Beyond that, the description discloses the core behavior: it normalizes raw sound-event counts to a per-observation-hour rate so two blocks of different lengths can be compared. It does not state what happens if the counting methods differ, but the schema's required 'gleiche_zaehlweise' parameter already surfaces that constraint.

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

Conciseness5/5

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

A single compact sentence that front-loads the action and scope with no filler. The bilingual phrasing is slightly unusual but earns its place by pairing the German domain wording with a clear English normalization statement.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a pure read-only calculation with five required, fully documented parameters and no output schema, the description supplies enough context to call it correctly. The missing piece is the exact return shape, but the tool name and the phrase 'Normalize ... to an observation hour' make the output concept clear enough.

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 the schema already documents all five parameters in detail, including ranges and the meaning of the boolean validation flag. The description adds only the high-level framing of comparing two uneven observation blocks; it does not add syntax or format details beyond what the schema provides. Baseline 3 is appropriate.

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 verb (Vergleicht/Normalize) and resource (Häufigkeiten markierter Spitzen / recorded sound-event counts) and clarifies that it works across two observation blocks of different lengths. It does not explicitly distinguish itself from any sibling, but the computational purpose 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'aus zwei verschieden langen aktiven Beobachtungen' implies the tool is for comparing two observation blocks with unequal durations, which gives implied usage context. However, there is no explicit when-to-use guidance, no exclusions, and no named alternative for cases like equal durations or single-block normalization.

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