Skip to main content
Glama

getecoback-raumklima

geraeuschereignis_zwei_hoerplaetze_synchron

Read-only

Findet die zeitgleiche Überdeckung eines protokollierten Geräusches an zwei Hörplätzen — Quantify overlap between event observations at two listening positions.

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_start": "<a_start>",
      "a_ende": "<a_ende>",
      "b_start": "<b_start>",
      "b_ende": "<b_ende>",
      "uhren_abgeglichen": "<uhren_abgeglichen>"
    },
    "name": "geraeuschereignis_zwei_hoerplaetze_synchron"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_endeYesBeobachtetes Ende am ersten Hörplatz in Sekunden.
b_endeYesBeobachtetes Ende am zweiten Hörplatz in Sekunden.
a_startYesBeobachteter Start am ersten Hörplatz in Sekunden.
b_startYesBeobachteter Start am zweiten Hörplatz in Sekunden.
uhren_abgeglichenYesGemeinsamer Zeitbezug und dieselbe Ereignisdefinition an beiden Plätzen?

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 safety profile is covered. The description adds that the tool computes coincidence of observations, but it is silent on the crucial behavior tied to the required uhren_abgeglichen flag (what happens when clocks are not aligned — error, no result, caveat) and on what the overlap quantity looks like when intervals do not intersect, which for a read-only computed tool is the main remaining behavioral unknown.

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?

One front-loaded sentence with no filler, though the German/English duplication repeats the same content twice rather than using the second sentence to add detail such as output semantics.

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?

With five required parameters, a gating boolean, and no output schema, the description explains what is computed but not what is returned (a duration in seconds, a boolean, or a fraction) nor the consequence of unaligned clocks. The tool is simple enough that this is adequate rather than fatal, but the result shape is a real 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 all five parameters are documented there with units, ranges, and meaning, so the description correctly does not duplicate them. It adds no interpretation of its own beyond the general notion of two observation intervals.

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 specific operation (finding/quantifying the temporal overlap of one logged noise event observed at two listening positions), which is concrete enough for an agent to grasp immediately. It does not name or distinguish itself from near siblings such as geraeuschereignis_sel_und_zeitfenster_abgleichen or geraet_geraeuschlog_zwei_uhranker_abgleichen, so differentiation is left implicit.

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 to use this tool versus clock-alignment or time-window comparison siblings, and no prerequisites beyond what is buried in the schema. Usage is only inferable from the single sentence describing the overlap computation.

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