Skip to main content
Glama

getecoback-climate-weather

raumtuer_schallmessung_a_b

Read-only

An einem Nachbarraumpunkt den Unterschied zwischen offener und geschlossener Innentür messen — Report the measured adjacent-room level difference with one door open versus closed.

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": {
      "offen_dba": "<offen_dba>",
      "geschlossen_dba": "<geschlossen_dba>",
      "gleicher_betriebspunkt": "<gleicher_betriebspunkt>"
    },
    "name": "raumtuer_schallmessung_a_b"
  }
}

Input Schema

NameRequiredDescriptionDefault
offen_dbaYesGleichartig gemessener A-bewerteter Pegel bei offener Tür am Vergleichsort.
geschlossen_dbaYesPegel an exakt gleicher Stelle bei geschlossener Tür.
gleicher_betriebspunktYesGerätestufe, Messdauer, Sensorlage und andere Geräusche waren gleich?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/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 and environment scope are covered. The description adds real context beyond that: the measurement is site-local and compares two door states at the same adjacent-room point. It stops short of describing what the report contains or how the two values are combined into a difference.

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 description is short and front-loads the crucial setting (an adjacent-room point) and the compared condition. The only inefficiency is that the German and English sentences are near-duplicates, which adds length without new information. Structure is otherwise clean with no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read-only report tool with three fully documented required parameters and no output schema, the description covers the essential scope and the compared quantities. Missing guidance is limited to output expectations and sibling routing, both minor at this complexity level. It is sufficient to call the tool correctly.

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 three parameters, their bounds, and the same-operating-point condition are already fully documented in structured form. The description only reinforces the open-versus-closed comparison conceptually and adds no syntax, unit, or tolerance guidance beyond the schema. 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?

The description names a specific action on a specific resource: measuring the level difference at an adjacent-room point with the interior door open versus closed, and reporting that measured difference. The German and English sentences agree, so the intent is unambiguous. It does not, however, contrast itself with related sibling measurement tools, so an agent gets a clear purpose but no differentiator.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance, and no alternative tool is named despite several sibling measurement tools existing. The only situational constraint (measurement at a comparison point with identical device setting) is implied rather than stated as a precondition. The agent must infer the calling context from the name alone.

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