Skip to main content
Glama

getecoback-raumklima

schallpegel_drei_einzelquellen_modellsumme

Read-only

Schätzt den gleichzeitigen Gesamtpegel aus drei separaten unabhängigen Beiträgen am selben Ort — Estimate three independent simultaneous source contributions at one location.

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": {
      "a": "<a>",
      "b": "<b>",
      "c": "<c>",
      "voraussetzungen_belegt": "<voraussetzungen_belegt>"
    },
    "name": "schallpegel_drei_einzelquellen_modellsumme"
  }
}

Input Schema

NameRequiredDescriptionDefault
aYesGetrennt ermittelter LAeq-Beitrag A in dB.
bYesGetrennt ermittelter LAeq-Beitrag B in dB.
cYesGetrennt ermittelter LAeq-Beitrag C in dB.
voraussetzungen_belegtYesUnabhängige Beiträge ohne mehrfachen Hintergrund, gleicher Ort, Gewichtung und Betriebszustand?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description successfully informs the agent that the calculation is a modeling task involving the summation of independent sources, which provides crucial context beyond the read-only annotation. While annotations cover the read-only nature, the description clarifies the underlying physics of the operation.

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?

The description is highly efficient, using one clear sentence in both German and English to front-load the essential function and scope. There is no unnecessary jargon or filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity of a sound pressure level modeling tool, the description is remarkably complete. It defines the core model constraints (three independent, simultaneous sources) which is all an agent needs to confidently invoke the tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description clarifies the physical meaning of the numeric parameters A, B, and C as 'LAeq-Beitrag', linking them to the total calculation. It also explains the semantic requirement of the 'voraussetzungen_belegt' boolean, adding significant value beyond the 100% schema coverage baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The tool clearly states it estimates the total sound level (Schallpegel) based on specific input conditions (three independent sources at one location). This distinguishes its purpose precisely from other potential acoustic calculation tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description is explicit about the required operational context: the inputs must be three independent contributions occurring simultaneously at the same location. This provides clear 'when to use' criteria based on the physical model.

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