Skip to main content
Glama

getecoback-raumklima

raumgeraeusch_eigenes_pegelziel_zusatzbeitrag

Read-only

Leitet aus bestehendem Pegel und eigenem Ziel einen modellierten Zusatzbeitrag ab — Estimate an independent added source budget under a chosen total level.

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": {
      "basis_db": "<basis_db>",
      "eigenes_ziel_db": "<eigenes_ziel_db>",
      "unabhaengiger_zusatz": "<unabhaengiger_zusatz>"
    },
    "name": "raumgeraeusch_eigenes_pegelziel_zusatzbeitrag"
  }
}

Input Schema

NameRequiredDescriptionDefault
basis_dbYesGemessenes LAeq-Mittel der bestehenden Geräusche in dB.
eigenes_ziel_dbYesSelbst gewählter Vergleichswert für dasselbe LAeq-Mittel in dB.
unabhaengiger_zusatzYesIst die zusätzliche Quelle als unabhängiger Beitrag zum selben Zeitfenster modellierbar?

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 real value by marking the result as 'modelliert' (an estimate, not a measurement) and framing it as an 'independent' contribution, which discloses the underlying assumption. It does not say what happens when the independence gate is false or what the returned number represents.

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 sentences, front-loaded with the derivation logic and followed by an English restatement. The bilingual gloss is partly redundant but defensible for a German-named tool; there is no filler beyond that.

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?

A simple, annotation-covered, three-parameter computation with no output schema, so the burden is modest. Still, the definition leaves the agent unsure what the derived value means physically and how the boolean gate changes the outcome, which matters for a tool whose entire purpose is producing a number.

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 baseline is 3. The description maps 'bestehendem Pegel' to basis_db and 'eigenem Ziel' to eigenes_ziel_db, but it says nothing about the third and most semantically loaded parameter, the unabhaengiger_zusatz boolean that gates whether the model applies at all.

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 specific verb and derived artifact: 'Leitet aus bestehendem Pegel und eigenem Ziel einen modellierten Zusatzbeitrag ab' plus the English gloss 'Estimate an independent added source budget under a chosen total level.' The operation (deriving a modeled add-on contribution from a measured baseline and a self-chosen target) is discernible, but it never names a sibling tool or clarifies how it differs from neighbouring acoustic-calculation tools, so it stops short of 5.

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 explicit when-to-use statement, no prerequisites, and no named alternative. The phrase 'under a chosen total level' hints at the scenario but leaves the agent to infer that this is a planning/estimation step rather than a measurement.

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