Skip to main content
Glama

getecoback-raumklima

luftreiniger_cadr_wert_pruefvergleich

Read-only

Veröffentlichte CADR-Werte nur für übereinstimmende Partikelkategorie, Stufe und Prüfbasis vergleichen — Check comparability of advertised CADR for the required particle category and operating setting.

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_m3_h": "<a_m3_h>",
      "b_m3_h": "<b_m3_h>",
      "partikel_gleich": "<partikel_gleich>",
      "stufe_gleich": "<stufe_gleich>",
      "methode_gleich": "<methode_gleich>"
    },
    "name": "luftreiniger_cadr_wert_pruefvergleich"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_m3_hYesAusgewiesener Partikel-CADR A in Kubikmeter pro Stunde.
b_m3_hYesAusgewiesener Partikel-CADR B in Kubikmeter pro Stunde.
stufe_gleichYesBetreffen beide Werte die zu vergleichende Betriebsstufe?
methode_gleichYesIst die Prüfmethode für beide Werte vergleichbar dokumentiert?
partikel_gleichYesSind die Partikelkategorien der zwei Werte gleich?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/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 important constraint that only advertised/published values are compared and only when categories match, but it omits the central behavior: whether a false comparability flag produces an error, a 'not comparable' result, or a partial comparison.

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 tight sentence with the gating condition front-loaded, plus an English mirror for clarity. The bilingual duplication is mild redundancy but not wasteful enough to obscure the call.

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 five required parameters and no output schema, the definition should clarify the non-comparable outcome and the result shape (e.g., delta or pass/fail). It covers the inputs' intent but leaves the decisive behavioral case undocumented.

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 each parameter (a_m3_h, b_m3_h, partikel_gleich, stufe_gleich, methode_gleich) is already documented at the field level. The description restates the three comparison dimensions but adds no unit conventions or semantics beyond what the schema provides, so the 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 concrete verb (vergleichen/compare) and a concrete resource (veröffentlichte CADR-Werte) and scopes it to matching particle category, stage, and test basis. That distinguishes it from the broader raumcheck or zweistufen_aussenluftvergleich siblings without naming them, so it is clear but lacks explicit sibling differentiation.

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?

Usage is implied by the precondition 'nur für übereinstimmende Partikelkategorie, Stufe und Prüfbasis', which tells the agent the comparison is conditional, but there is no explicit when-to-use vs. when-to-use-another-tool guidance. The two boolean gates are effectively usage conditions, yet the description never says what to do when one is false.

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