Skip to main content
Glama

getecoback-climate-weather

geraeuschzeit_luecken_bei_zwei_markierten_spitzen

Read-only

Findet den längsten durchgehend beobachteten Abschnitt außerhalb zweier markierter Geräusche — Find the longest observed gap outside two recorded sound events.

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": {
      "gesamt_sek": "<gesamt_sek>",
      "erster_start": "<erster_start>",
      "erstes_ende": "<erstes_ende>",
      "zweiter_start": "<zweiter_start>",
      "zweites_ende": "<zweites_ende>"
    },
    "name": "geraeuschzeit_luecken_bei_zwei_markierten_spitzen"
  }
}

Input Schema

NameRequiredDescriptionDefault
gesamt_sekYesDauer der lückenlos beobachteten Folge in Sekunden.
erstes_endeYesEnde des ersten Ereignisses in Sekunden.
erster_startYesBeginn des ersten Ereignisses in Sekunden.
zweites_endeYesEnde des zweiten Ereignisses in Sekunden.
zweiter_startYesBeginn des zweiten Ereignisses in 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 the safety profile is covered and the bar is lower. The description adds real semantic content — that the gap must be 'durchgehend beobachtet' (contiguously observed) within the total window and that it is the longest such gap — but says nothing about what is returned (duration vs. start/end pair) or behavior with invalid/overlapping ordering.

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?

The core semantics are front-loaded and the sentence is tight; the German/English duplication is redundant for a single-language reader but standard practice and adds no noise that obscures the point.

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 pure computation tool with no output schema, the description should clarify the result shape (e.g., a duration in seconds, or the free interval endpoints) and behavior when the two events overlap or touch — neither is covered. What it does state is accurate, so this is a clear but modest gap.

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% and each of the five required second-based fields is documented in the schema, so the schema carries the parameter burden. The description corroborates that two events and an observation span are involved but adds no unit, ordering, or boundary conventions beyond that.

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 gives a specific verb+result ('Findet den längsten ... Abschnitt', 'Find the longest observed gap') over a well-defined resource ('außerhalb zweier markierter Geräusche'). It is clearly a gap-finding computation, distinguishing it from interval-overlap or synchronization siblings, though it never names an alternative tool explicitly.

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 only implied: an agent can infer this is for locating the largest free window outside two events. There is no statement of when to prefer it over the many similarly named 'zwei ...' sibling tools, and no handling guidance for edge cases such as overlapping or adjacent events.

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