Skip to main content
Glama

getecoback-climate-weather

geraeuschabstand_gemessen_gegen_freifeld

Read-only

Vergleicht eine tatsächlich gemessene Pegelabnahme mit einer Freifeld-Referenz — Compare measured level attenuation with an ideal free-field 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": {
      "nah_m": "<nah_m>",
      "fern_m": "<fern_m>",
      "nah_db": "<nah_db>",
      "fern_db": "<fern_db>",
      "gleiche_richtung": "<gleiche_richtung>"
    },
    "name": "geraeuschabstand_gemessen_gegen_freifeld"
  }
}

Input Schema

NameRequiredDescriptionDefault
nah_mYesNaher Abstand in Metern.
fern_mYesWeiterer Abstand in Metern.
nah_dbYesGemessener LAeq am nahen Punkt in dB.
fern_dbYesGemessener LAeq am weiteren Punkt in dB.
gleiche_richtungYesEin Messstrahl, gleiche Ausrichtung, Quelle und vergleichbare Hintergrundbedingungen?

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 this is a comparison against an ideal reference rather than a simulation, but it says nothing about the consequence of 'gleiche_richtung' being false, whether such input is rejected or flagged, or what the comparison produces — meaningful behavioral gaps for a validation tool.

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 clauses, front-loaded with the core comparison, with no filler. The German sentence is immediately repeated in English, which is redundant for the agent but does not obscure the meaning.

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 and no output schema, the description should say roughly what result comes back (a deviation in dB, a pass/fail verdict) and how the 'gleiche_richtung' precondition affects it. It covers the input concept but leaves the outcome unspecified, which is a substantive gap for a computation 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%, so all five parameters are already documented in the schema, which sets the baseline at 3. The description only supplies the framing that nah/fern distance and nah/fern dB form two matched measurement points to be compared, without adding units, tolerances, or validity conditions beyond the schema.

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 on a specific quantity: comparing measured level attenuation ('gemessene Pegelabnahme') against an ideal free-field reference. That is clear enough to distinguish it from a generic measurement reader. It does not, however, differentiate itself from the closely related sibling 'klima_schallabstand_freifeld_szenario', which sounds like it covers the same free-field domain.

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 this tool should be used, when it should not, or which sibling to pick for a scenario/planning computation versus a measured-data check. The agent must infer that this is for post-measurement validation from the word 'gemessen' alone.

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