Skip to main content
Glama

getecoback-climate-weather

luftreiniger_cadr_raumcheck

Read-only

Hersteller-CADR auf das gemessene Raumvolumen beziehen — Estimate equivalent particulate clean-air delivery in a measured room.

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": {
      "cadr_m3_h": "<cadr_m3_h>",
      "volume_m3": "<volume_m3>"
    },
    "name": "luftreiniger_cadr_raumcheck"
  }
}

Input Schema

NameRequiredDescriptionDefault
cadr_m3_hYesDokumentierte CADR für Partikel und die betrachtete Gerätestufe in m³/h, nicht der ungefilterte Lüfterstrom.
volume_m3YesGemessenes Volumen des betrachteten Raums in m³.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true and openWorldHint=false, so a pure, side-effect-free calculation is expected and the description does not contradict that. The description adds the useful scoping hint that this concerns particulate CADR in a measured room, but says nothing about assumptions (e.g. ignoring gas-phase CADR, ignoring real-world decay, or how the result is normalized). Given annotations carry the safety profile, a 3 reflects modest added value.

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 compact bilingual sentence, front-loaded with the operation and free of filler. It is arguably too terse rather than bloated; nothing needs removing, but a short clause on the returned metric would earn its space.

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 only two fully described parameters, no nested objects, and a simple read-only computation, the definition is close to sufficient. The main gap is that no output schema exists and the description never says what number comes back or in what unit, which is precisely the information a caller of a calculator needs.

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%: both cadr_m3_h and volume_m3 are documented with units, ranges, and the important caveat that CADR must be the documented particle-stage value, not unfiltered fan throughput. The description adds no further parameter meaning beyond that, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a concrete operation (relating manufacturer CADR to measured room volume) and a resource (a room's measured volume), so the inputs are identifiable. However, for a calculation tool it never states what quantity is produced — equivalent clean-air delivery stated in what unit, or an air-change rate — leaving the actual output ambiguous. The title/name alone would not convey this, so the description does most of the work but stops short of a precise deliverable.

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 guidance on when to use this versus not, no prerequisites (e.g. that a room measurement must already exist), and no mention of any sibling or alternative for gas-phase or filter-lifetime questions. The agent must infer usage purely from the parameter names.

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