Skip to main content
Glama

getecoback-climate-weather

klimageraet_schallzeit_mittel_zwei_phasen

Read-only

Zwei vergleichbare Schall-Zeitmittel eines Klimageräts über ihre Zeitanteile zusammenfassen — Combine two separately measured equivalent A-weighted levels on an energy basis.

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_laeq_dba": "<a_laeq_dba>",
      "a_dauer_s": "<a_dauer_s>",
      "b_laeq_dba": "<b_laeq_dba>",
      "b_dauer_s": "<b_dauer_s>",
      "messart_gleich": "<messart_gleich>"
    },
    "name": "klimageraet_schallzeit_mittel_zwei_phasen"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_dauer_sYesGemessene Dauer der Phase A in Sekunden.
b_dauer_sYesGemessene Dauer der Phase B in Sekunden.
a_laeq_dbaYesÄquivalenter A-bewerteter Dauerschallpegel LAeq in Phase A.
b_laeq_dbaYesÄquivalenter A-bewerteter Dauerschallpegel LAeq in Phase B.
messart_gleichYesWurden beide Pegel als LAeq mit gleicher Messposition und Einstellung in getrennten Phasen erfasst?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations declare readOnlyHint=true and openWorldHint=false, so safety is already covered; the description usefully adds that the combination is energy-based and duration-weighted, which is genuine behavioral context. It does not state what happens when messart_gleich is false (refusal? error?) and, with no output schema, says nothing about the returned quantity or its unit.

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?

One front-loaded sentence with the core action first and the method qualifier second; nothing is padded. The German and English clauses largely restate the same content, which is mild redundancy, though the English version adds the explicit 'energy basis' formulation.

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?

With no output schema, the description should indicate the shape of the result (a single combined LAeq, presumably with unit), and it does not. For a pure computation tool whose five required parameters are fully documented in the schema, this is the main remaining gap; behavior on the messart_gleich=false path is likewise unstated.

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?

Schema coverage is 100%, so baseline is 3, but the description adds real meaning beyond the schema: 'über ihre Zeitanteile' clarifies that a_dauer_s and b_dauer_s act as weights rather than simple limits, and 'vergleichbare' gives purpose to the messart_gleich flag. This explains how the five inputs interact, not just what each one is.

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?

A concrete verb plus resource: 'Zwei vergleichbare Schall-Zeitmittel ... zusammenfassen' and 'Combine two separately measured equivalent A-weighted levels on an energy basis.' It also names the method (energy basis / Zeitanteile), which distinguishes it from a plain single-measurement time-averaging sibling such as klimageraet_geraeusch_zeitmittel. It stops short of explicitly naming which sibling to use instead, so it is clear but not fully differentiated.

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 word 'vergleichbare' and the messart_gleich requirement imply a precondition (both levels measured with identical position/settings in separate phases), but this is only implicit and never spelled out as a when-to-use rule. No when-not-to-use case and no alternative tool is referenced, so routing depends on inference from the name and schema.

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