Skip to main content
Glama

getecoback-raumklima

raumreflexion_zweitimpuls_wegdifferenz_modell

Read-only

Schätzt aus einem bereits aufgezeichneten Zeitabstand eine mögliche zusätzliche Schallstrecke — Estimate excess acoustic path length from an existing delayed sound marker.

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": {
      "verzoegerung_ms": "<verzoegerung_ms>",
      "schalltempo_m_s": "<schalltempo_m_s>",
      "gemeinsames_ereignis_belegt": "<gemeinsames_ereignis_belegt>"
    },
    "name": "raumreflexion_zweitimpuls_wegdifferenz_modell"
  }
}

Input Schema

NameRequiredDescriptionDefault
schalltempo_m_sYesFür die Rechenannahme gewählte Schallgeschwindigkeit in m/s.
verzoegerung_msYesZeitabstand zweier Marker derselben Aufnahme in Millisekunden.
gemeinsames_ereignis_belegtYesBeide Marken stammen nach vorhandenem Beleg vom selben kurzen Ereignis?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/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 and locality profile is settled. The description adds that the result is an estimate ('Schätzt', 'mögliche'), i.e. model-based rather than measured, but says nothing about precision, assumptions, or what invalidates the estimate beyond what the schema's boolean already implies.

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 bilingual sentence with the computation front-loaded and zero filler. Nothing is restated and nothing extraneous is included.

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?

The tool is simple and fully annotated, and parameters are well documented, but with no output schema the description never states what unit or form the returned path length takes, nor how the three inputs combine. That is a meaningful omission for a calculation tool.

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 parameter carries its own description including units and valid ranges, so the schema does the heavy lifting. The description adds no per-parameter meaning, such as how the boolean gate interacts with the result, so 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 pairs a specific verb ('Schätzt' / 'Estimate') with a specific quantity ('mögliche zusätzliche Schallstrecke' / 'excess acoustic path length') and names its input ('aus einem bereits aufgezeichneten Zeitabstand'). An agent knows exactly what computation is performed, though nothing in the text separates it from any of the numerous topically adjacent sibling tools.

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: the phrase 'aus einem bereits aufgezeichneten Zeitabstand' signals that an already-recorded delay marker must exist before calling, which is a genuine prerequisite. There is no explicit statement of when to prefer this tool over an alternative, nor any exclusion or follow-up guidance.

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