Skip to main content
Glama

getecoback-raumklima

klima_schallabstand_freifeld_szenario

Read-only

Relative Änderung bei zwei Abständen im idealisierten Freifeld berechnen — Estimate distance-only sound-level change for an ideal point source outside.

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": {
      "referenz_m": "<referenz_m>",
      "ziel_m": "<ziel_m>",
      "freie_sicht_ohne_reflexion": "<freie_sicht_ohne_reflexion>"
    },
    "name": "klima_schallabstand_freifeld_szenario"
  }
}

Input Schema

NameRequiredDescriptionDefault
ziel_mYesZweiter Abstand derselben Quelle in Metern.
referenz_mYesErster Abstand derselben Quelle in Metern.
freie_sicht_ohne_reflexionYesSoll ausdrücklich freie Ausbreitung ohne Wände, Vorsprünge oder angekoppelte Schwingungen betrachtet werden?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/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 and the bar is lower. The description adds the meaningful modelling assumptions (ideal point source, idealized free field, distance-only). It leaves undisclosed what happens when freie_sicht_ohne_reflexion is false, and the return value is never characterized.

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 compact clauses with the operation and the modelling constraint front-loaded; nothing is padded. The German and English halves are near-duplicates, which is defensible for a bilingual toolset but costs a small amount of density.

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?

For a small three-parameter calculation with full schema coverage and safe-read annotations, the description covers the modelling premise well. With no output schema, however, it should say whether the result is a dB delta or a factor and in which direction, and it should explain the effect of the free-field boolean; both are left open.

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 coverage is 100%, so all three parameters are already self-documenting, and the baseline of 3 applies. The description reinforces that the two distance parameters are a reference/target pair for the same source and that only distance variation counts, but it adds no units, range, or interpretation 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?

States a concrete verb and resource: compute the relative change for two distances in an idealized free field, plus the English gloss 'estimate distance-only sound-level change for an ideal point source'. That is specific enough for an agent to pick it out from the neighbouring klima/abluft tools. It does not explicitly name a sibling it must not be confused with, so it stays below 5.

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 implied rather than stated: 'idealized free field' and 'distance-only' tell the agent to call it only when distance is the sole variable, and 'outside' hints at the outdoor case. There is no explicit when-not condition and no named alternative for indoor, wall-adjacent, or reflection-affected estimates.

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