Skip to main content
Glama

getecoback-climate-weather

luftreiniger_zweistufen_aussenluftvergleich

Read-only

Für hohen Vorlauf und leiseren Weiterbetrieb das äquivalente Partikelfiltervolumen getrennt von der Außenluftbilanz berechnen — Estimate the clean-air contribution of a high and a quiet filter phase without counting fresh air.

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": {
      "vorlauf_cadr": "<vorlauf_cadr>",
      "vorlauf_min": "<vorlauf_min>",
      "leise_cadr": "<leise_cadr>",
      "leise_min": "<leise_min>",
      "raum_m3": "<raum_m3>"
    },
    "name": "luftreiniger_zweistufen_aussenluftvergleich"
  }
}

Input Schema

NameRequiredDescriptionDefault
raum_m3YesRaumvolumen in m³.
leise_minYesDauer der leisen Stufe. In Minuten.
leise_cadrYesBestätigter CADR der leisen Stufe in m³/h.
vorlauf_minYesDauer der hohen Stufe. In Minuten.
vorlauf_cadrYesBestätigter CADR der hohen Stufe 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 safety and locality are covered. The description contributes one genuine behavioral fact beyond that: fresh-air contribution is deliberately excluded from the calculation. It says nothing about units of the result or how the two phases are combined, which a computation tool could usefully disclose.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, but the German and English versions restate the same content rather than complementing each other, and the em-dash construction buries the operative verb. Nothing is padded to the point of noise, yet the bilingual duplication is not free.

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?

It is a pure five-parameter calculator with full schema documentation and a read-only annotation, so most of the burden is already met elsewhere. The description still leaves the agent guessing about the returned quantity's unit and how the two phases are aggregated, which matters since there is no output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and each of the five numeric parameters carries its own unit and range note, so the schema does the heavy lifting. The description adds a small amount by framing the parameters as two phase pairings (high CADR/duration vs quiet CADR/duration) plus a room volume, but no syntax or formula detail beyond that. Slightly above the baseline 3 because it clarifies the pairing semantics.

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 definition names a specific computation: the equivalent particle-filter volume for a high (Vorlauf) and a quiet filter phase, explicitly excluding the fresh-air balance. The English half ('estimate the clean-air contribution of a high and a quiet filter phase without counting fresh air') is crisp and lets an agent tell this apart from CADR room-check siblings. The German half is jargon-heavy and partially redundant, but the operation is identifiable.

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 scope condition ('ohne Außenluftbilanz' / 'without counting fresh air') implies when this tool applies — two-stage operation where ventilation should not be credited. However, it never names an alternative sibling or states when NOT to use it, so the routing signal must be inferred from the sibling 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