Skip to main content
Glama

getecoback-raumklima

geraeuschquellen_gleichzeitigkeit_erwartungsreferenz

Read-only

Vergleicht beobachtete Gleichzeitigkeit zweier Geräuschquellen mit einem einfachen Unabhängigkeitsmodell — Compare observed source overlap with an independent occupancy reference.

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>",
      "a_sek": "<a_sek>",
      "b_sek": "<b_sek>",
      "beide_sek": "<beide_sek>"
    },
    "name": "geraeuschquellen_gleichzeitigkeit_erwartungsreferenz"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_sekYesBelegte Dauer von Quelle A in Sekunden.
b_sekYesBelegte Dauer von Quelle B in Sekunden.
beide_sekYesBeobachtete gemeinsame Dauer aus derselben Zeitachse in Sekunden.
gesamt_sekYesDauer der gemeinsamen Beobachtung in Sekunden.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/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 by structure. The description adds the one genuinely useful behavioral fact: the reference is a *simple independence* model, hinting that the baseline is an assumption rather than a measurement. It does not disclose how the comparison is expressed, nor what happens when beide_sek is inconsistent with a_sek/b_sek.

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

Conciseness3/5

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

The description is short and front-loaded, but the English clause is a near-verbatim translation of the German one, so half the text carries no new information. It is not bloated, but it is also not dense with signal.

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?

With no output schema and four required numeric inputs, the description is the only place a caller could learn what comes back — and it says nothing about the result form or how to interpret it. For a computation tool whose entire value is the returned comparison, that is a material 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%, so the four duration parameters are already fully documented, including the 'same time axis' constraint on beide_sek. The description adds only the framing that one operand is observed and the other is a model, which is marginal beyond the schema. Baseline 3 applies.

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 verb ("Vergleicht") and both operands: the observed overlap of two noise sources and an independent-occupancy reference model. That is enough to separate it from the sibling list, which contains no other simultaneity/occupancy comparison. It stops short of saying what form the comparison takes (ratio, deviation, verdict).

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 guidance on when to use this tool, when not to, or what alternative exists for related questions. The only implicit constraint — that all four durations must come from the same observation window — is buried in the German noun phrase and repeated only obliquely in English.

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