Skip to main content
Glama

getecoback-climate-weather

luftreiniger_cadr_watt_paarbeleg

Read-only

Einen veröffentlichten CADR und die Leistungsaufnahme derselben Betriebsstufe als Quotient einordnen — Compute clean air delivery per watt only for a documented matching mode.

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>",
      "leistung_w": "<leistung_w>",
      "stufe_gleich": "<stufe_gleich>",
      "pruefung_dokumentiert": "<pruefung_dokumentiert>"
    },
    "name": "luftreiniger_cadr_watt_paarbeleg"
  }
}

Input Schema

NameRequiredDescriptionDefault
cadr_m3_hYesVeröffentlichter Partikel-CADR in Kubikmeter pro Stunde.
leistung_wYesDokumentierte elektrische Leistungsaufnahme in Watt.
stufe_gleichYesSind beide Werte der gleichen Stufe und dem gleichen Filterzustand zugeordnet?
pruefung_dokumentiertYesIst der Partikeltest und der dazugehörige Betriebspunkt erkennbar?

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 establish readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds the constraint that both values must belong to the same documented stage, but it does not say what the tool does when stufe_gleich or pruefung_dokumentiert is false (refuse, error, warn) nor what the returned quotient looks like.

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?

Two compact clauses, with the computation stated first and the applicability restriction second, so nothing is buried. The bilingual repetition is slightly redundant but costs little and aids matching in either language.

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?

For a four-required-parameter read-only calculator with no output schema, the description covers the inputs' intent but leaves the result undefined — no output unit (e.g. m³/h per W) and no behavior on failed preconditions. An agent can call it correctly but cannot anticipate the response.

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 all four parameters, their units and their bounds are already documented in the schema. The description reinforces the CADR and power-draw pairing and the 'documented matching mode' precondition, but adds no unit or validation detail beyond the structured fields.

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 computation (published CADR divided by power draw of the same operating stage, expressed as a quotient) rather than restating the tool name. It is clearly distinct from siblings like luftreiniger_cadr_raumcheck or luftreiniger_cadr_wert_pruefvergleich, though it never names an alternative explicitly.

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?

The phrase 'only for a documented matching mode' gives an explicit gating condition for when this tool applies, which is strong for a narrowly scoped calculator. It stops short of naming a sibling to use when the mode does not match or the test is undocumented.

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