Skip to main content
Glama

getecoback-climate-weather

klimaanlage_geraeusch_vergleich

Read-only

Zwei Geräuschwerte nur bei gleicher Messgröße und vergleichbaren Bedingungen einordnen — Compare AC noise figures on a like-for-like 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": {
      "pegel_a_dba": "<pegel_a_dba>",
      "pegel_b_dba": "<pegel_b_dba>",
      "groesse_a": "<groesse_a>",
      "groesse_b": "<groesse_b>",
      "gleiche_bedingungen": "<gleiche_bedingungen>"
    },
    "name": "klimaanlage_geraeusch_vergleich"
  }
}

Input Schema

NameRequiredDescriptionDefault
groesse_aYesMessgröße der Angabe A.
groesse_bYesMessgröße der Angabe B.
pegel_a_dbaYesAngegebener Pegel A in dB(A).
pegel_b_dbaYesAngegebener Pegel B in dB(A).
gleiche_bedingungenYesBetriebsmodus und Messbedingungen sind vergleichbar, bei Schalldruck auch Position und Abstand?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/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 the substantive behavior that this is a validity-gated assessment (results only mean something under matched metrics/conditions), but it never says what the tool does when the gate is not met — refuse, flag, or return a caveated result — which matters for a tool with no output schema.

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 constraint stated before the action, which is the right order. The German/English duplication is redundant for a single reader but is a deliberate bilingual convention rather than filler.

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?

All five required parameters are fully documented and the read-only nature is covered by annotations, so the core call is callable from the definition. The gap is the outcome semantics for the mismatch case (e.g. groesse 'unbekannt' or gleiche_bedingungen=false), which is exactly the situation this tool is built around and which no output schema explains.

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 coverage is 100% and the enum values and the gleiche_bedingungen question are already documented in the schema, so the baseline is 3. The description reinforces that groesse_a/groesse_b must match for a meaningful comparison, but it adds no format or interpretation detail beyond that.

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?

The description gives a specific verb and resource: 'Zwei Geräuschwerte ... einordnen' / 'Compare AC noise figures', so the agent knows this assesses two noise readings against each other rather than computing an unrelated HVAC value. It does not name a sibling it replaces, but the scope (noise-figure comparison) is distinct enough from the listed sibling names.

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

Usage Guidelines4/5

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

It states the governing precondition clearly: only compare when the measurement quantity is identical and conditions are comparable ('nur bei gleicher Messgröße und vergleichbaren Bedingungen'). That tells the agent when the tool is applicable, though it does not say what to do when the precondition fails or point to any alternative tool.

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