Skip to main content
Glama

getecoback-climate-weather

geraeuschspitzen_getrennte_ereignisfenster

Read-only

Ordnet zwei aufgezeichnete Ereignisse nach sichtbarer zeitlicher Trennung ein — Decide whether two recorded sound events are distinguishable in time.

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": {
      "ende_a_sek": "<ende_a_sek>",
      "beginn_b_sek": "<beginn_b_sek>",
      "ende_b_sek": "<ende_b_sek>",
      "trennzeit_sek": "<trennzeit_sek>"
    },
    "name": "geraeuschspitzen_getrennte_ereignisfenster"
  }
}

Input Schema

NameRequiredDescriptionDefault
ende_a_sekYesEnde des ersten beobachteten Ereignisses in Sekunden.
ende_b_sekYesEnde des folgenden Ereignisses in Sekunden.
beginn_b_sekYesBeginn des folgenden beobachteten Ereignisses in Sekunden.
trennzeit_sekYesFür das Protokoll gewählte Mindestpause zur eindeutigen Trennung in Sekunden.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/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 safety profile is covered without description help. The description adds the decision framing (a comparison, not a mutation), but says nothing about the result — whether it returns a boolean, a verdict string, or a recomputed gap — nor about tolerance or rounding. With annotations carrying the safety burden, a 3 is appropriate.

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?

Two short sentences with zero padding, and the decision framing is front-loaded. The German/English duplication is a minor redundancy, but for a German-named tool it aids comprehension rather than wasting space.

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

Completeness2/5

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

There is no output schema, so the description carries the full burden of telling the agent what comes back — and it does not. For a predicate-style tool with four required time parameters, the agent cannot tell whether to expect a boolean, a categorical verdict, or a computed margin against trennzeit_sek. That missing return semantics is a substantive gap for a tool of this 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 all four parameters (ende_a_sek, beginn_b_sek, ende_b_sek, trennzeit_sek) are already documented in the schema. The description adds no semantics beyond that — notably it never explains the comparison itself, i.e. that the gap between beginn_b_sek and ende_a_sek is checked against trennzeit_sek. Baseline 3 applies since the schema does the heavy lifting.

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 names a concrete operation on a concrete resource: deciding whether two recorded sound events are separable in time ('sichtbarer zeitlicher Trennung'). The bilingual restatement ('Decide whether two recorded sound events are distinguishable in time') reinforces rather than dilutes the verb+object pairing. It does not, however, distinguish itself from any sibling tool, 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 Guidelines2/5

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

There is no when-to-use guidance, no precondition (e.g. that both events must already be recorded within the same day window), and no statement about what to do when the answer is negative. The agent must infer the usage context entirely from the phrase 'zwei aufgezeichnete Ereignisse'. No alternative tool or fallback path is named.

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