Skip to main content
Glama

getecoback-climate-weather

klimageraet_geraeusch_zeitmittel

Read-only

Gemessene leisere und lautere Betriebsabschnitte energetisch mitteln — Combine distinct sound measurement periods into one time-weighted LAeq.

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_dba": "<a_dba>",
      "b_dba": "<b_dba>",
      "minuten_a": "<minuten_a>",
      "minuten_b": "<minuten_b>",
      "gleiche_messposition": "<gleiche_messposition>"
    },
    "name": "klimageraet_geraeusch_zeitmittel"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_dbaYesLAeq des ersten zusammenhängenden Betriebsabschnitts.
b_dbaYesLAeq des zweiten, nicht überlappenden Abschnitts am gleichen Messort.
minuten_aYesDauer des ersten Abschnitts in Minuten.
minuten_bYesDauer des zweiten Abschnitts in Minuten.
gleiche_messpositionYesDasselbe Messgerät, dieselbe A-Bewertung und gleiche Position?

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?

The annotations already establish readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds the energy-averaging concept, but it does not explain what happens when gleiche_messposition is false, whether the tool rejects or warns, or how the resulting LAeq is formatted. Useful context is added, but key behavioral details remain absent.

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?

The definition is a single compact bilingual sentence, front-loaded with the action and output concept. It wastes no words, though its terseness contributes to the missing usage and behavioral details.

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?

This is a pure computation tool with a fully described five-parameter schema and read-only annotations, which covers much of the context. However, there is no output schema and the description does not explain the returned value's format, rounding, or the consequence of a false gleiche_messposition, leaving meaningful gaps for a calculation tool.

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%, with each of the five parameters documented in the input schema. The description adds only the high-level 'energetically' and 'time-weighted' framing, without parameter-level meaning beyond what the schema already supplies, so the baseline of 3 is appropriate.

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 action: energetically average quieter and louder operating periods into one time-weighted LAeq. The verb and resource are clear, but it does not explicitly differentiate this calculator from sibling noise tools such as klimaanlage_geraeusch_vergleich or klimageraet_geraeusch_hintergrund.

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 description implies usage by saying it combines distinct measurement periods, so an agent can infer that it is for merging two non-overlapping LAeq readings. However, it gives no explicit when-to-use guidance, no alternatives, and no exclusions, leaving the selection context mostly implicit.

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