Skip to main content
Glama

getecoback-climate-weather

klimageraet_geraeusch_hintergrund

Read-only

Geräuschanteil eines laufenden Klimageräts bei bekanntem Hintergrund abschätzen — Estimate the unit contribution from matched on/off sound recordings.

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": {
      "an_dba": "<an_dba>",
      "aus_dba": "<aus_dba>",
      "gleicher_hintergrund": "<gleicher_hintergrund>"
    },
    "name": "klimageraet_geraeusch_hintergrund"
  }
}

Input Schema

NameRequiredDescriptionDefault
an_dbaYesEnergieäquivalenter A-bewerteter Schalldruckpegel mit Gerät (LAeq).
aus_dbaYesHintergrundpegel ohne Gerät (LAeq) am gleichen Ort.
gleicher_hintergrundYesGleiche Messdauer, Position, Raum und gleichbleibende Hintergrundgeräusche?

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. The description adds that the result is an estimate derived from paired recordings, but it does not say what happens when gleicher_hintergrund is false (abort, warning, or silently invalid result), nor the physics behind the subtraction. With annotations carrying the safety profile, a 3 is appropriate.

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 core action first and the mechanism after, with no filler. The bilingual duplication is mildly redundant but aids disambiguation in a mixed-language tool set.

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?

There is no output schema, yet the description never states what is returned (a single corrected dB value, a range, or a validity flag), nor the behavior when the matched-conditions flag is false. For a small three-parameter computation this is adequate but leaves a real gap around the result and the failure path.

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% and the German parameter descriptions already define LAeq, the background level, and the matched-conditions flag. The description only supplies the overall framing of on/off pairing and adds no new meaning per parameter, so the baseline 3 applies.

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?

Names a specific verb and resource: estimating the noise contribution ('Geräuschanteil') of a running air-conditioning unit given a known background. The English clause adds the mechanism ('from matched on/off sound recordings'), so an agent knows this is a subtraction-style estimation. It does not explicitly differentiate itself from siblings such as klimageraet_geraeusch_zeitmittel or klimaanlage_geraeusch_vergleich, so it stops short of a 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?

The phrase 'bei bekanntem Hintergrund' and 'matched on/off sound recordings' implies the precondition: two comparable measurements, one with the unit on and one off. That is useful implied guidance, but there is no explicit when-to-use/when-not statement and no named alternative for cases where matched recordings are unavailable.

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