Skip to main content
Glama

getecoback-raumklima

luftreiniger_gleichzeitige_cadr_staffelung

Read-only

Bilanziert zwei nach gleicher Methode angegebene CADR im selben Raum mit versetzten Laufzeiten — Account for two comparable purifier ratings with staggered starts in one 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_a_m3h": "<cadr_a_m3h>",
      "cadr_b_m3h": "<cadr_b_m3h>",
      "nur_a_min": "<nur_a_min>",
      "beide_min": "<beide_min>",
      "nur_b_min": "<nur_b_min>"
    },
    "name": "luftreiniger_gleichzeitige_cadr_staffelung"
  }
}

Input Schema

NameRequiredDescriptionDefault
beide_minYesGemeinsame Laufzeit beider Geräte in Minuten.
nur_a_minYesLaufzeit nur von Gerät A in Minuten.
nur_b_minYesLaufzeit nur von Gerät B in Minuten.
cadr_a_m3hYesPartikel-CADR Gerät A in m³/h.
cadr_b_m3hYesPartikel-CADR Gerät B für gleiche Prüfmethode und Partikelfraktion in m³/h.

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 the agent knows this is a closed-world, side-effect-free computation. The description adds the real modelling constraint that both CADR values must come from the same measurement method and that runtimes are staggered, but it never says what the balance yields (a combined effective CADR? a delivered clean-air volume?) even though there is no output schema to compensate.

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 operation and its scope are front-loaded in a single sentence, with no padding. The German and English halves are near-verbatim duplicates, which is defensible for a bilingual tool set but does not add information.

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 five-parameter pure calculation with no output schema and only minimal annotations, the definition covers the inputs and the comparability constraint but leaves the result and its interpretation unstated. An agent can call it correctly but cannot judge what the returned balance represents or whether the three time windows must be mutually exclusive.

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%: all five parameters carry units, ranges and meaning, including the requirement that device B's CADR match device A's test method and particle fraction. The description adds little beyond that — it does not explain how the three time windows (nur_a_min, beide_min, nur_b_min) are sequenced or whether their sum is the total observation period, which is the one non-obvious semantic.

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?

"Bilanziert zwei ... CADR im selben Raum mit versetzten Laufzeiten" names a specific operation (a combined clean-air balance) on a specific resource (two comparable CADR ratings with staggered runtimes). It is clearly a two-device, one-room calculation, which separates it from single-device or separated-room siblings, but it never names an alternative such as raumcheck or taktbetrieb_reinluftbilanz, so the differentiation must be inferred.

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?

The scenario is embedded in the description — two purifiers with comparable ratings whose runtimes overlap only partially — which is enough to recognise when the tool applies. There is no explicit when-to-use/when-not statement, no prerequisite (e.g. ratings measured under the same test method must already be established) and no routing to sibling tools.

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