Skip to main content
Glama

getecoback-climate-weather

lueftung_oktavband_daempfungsbeleg_einzelpfad

Read-only

Rechnet einen ausdrücklich zusammengehörigen Quellen- und Einfügungsdämmwert nur für ein einzelnes Frequenzband — Apply documented attenuation to one octave band on the same source path.

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": {
      "quellenband_hz": "<quellenband_hz>",
      "daempfungsband_hz": "<daempfungsband_hz>",
      "lw_band_db": "<lw_band_db>",
      "daempfung_db": "<daempfung_db>",
      "pfad_vergleichbar": "<pfad_vergleichbar>"
    },
    "name": "lueftung_oktavband_daempfungsbeleg_einzelpfad"
  }
}

Input Schema

NameRequiredDescriptionDefault
lw_band_dbYesSchallleistung im Quellenband in dB.
daempfung_dbYesEinfügungsdämmung desselben Bands in dB.
quellenband_hzYesMittenfrequenz des belegt ungewichteten Quellenbands in Hz.
daempfungsband_hzYesMittenfrequenz des dokumentierten Einfügungsdämmwerts in Hz.
pfad_vergleichbarYesDerselbe Kanalpfad und dokumentiert vergleichbarer Bezug beider Werte?

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 safety is covered and "Rechnet" is consistent with a pure computation. The description leaves the decisive behavior unstated: what happens when the pairing does not hold (the required boolean pfad_vergleichbar implies a rejection or error path that is never described), and whether any result is computed or refused in that case.

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?

A single front-loaded sentence with the scope constraint placed after the operation; nothing is padded or redundant. The bilingual restatement costs little, though it repeats rather than extends the German clause.

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 5-parameter calculation tool with no output schema, the description should say what a successful call yields (an attenuated band level?) — it says only that something is "computed". The required-input gating and the rejection behavior remain undocumented, which leaves an agent guessing about outcomes.

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 schema already carries the parameter meaning and a baseline of 3 is appropriate. The description adds only the notion that source and attenuation values must belong together, without clarifying why quellenband_hz and daempfungsband_hz are separate inputs or how pfad_vergleichbar gates the call.

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?

"Rechnet einen ... Quellen- und Einfügungsdämmwert nur für ein einzelnes Frequenzband" gives a specific operation (applying documented attenuation) with an explicit scope limit (one octave band, one source path). The single-band restriction implicitly distinguishes it from a multi-band variant, though no sibling is named outright.

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?

The phrase "nur für ein einzelnes Frequenzband" and "ausdrücklich zusammengehörig" hints at when the tool applies (a single, explicitly paired band), but there is no stated when-not-to-use, no named alternative, and no instruction on what to do when several bands must be processed.

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