Skip to main content
Glama

getecoback-raumklima

luftwechsel_dauer_abschaetzen

Read-only

Lüftungsdauer aus bekanntem Außenluftstrom und Raumvolumen abschätzen — Estimate ventilation time for a target fresh-air fraction under perfect mixing.

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": {
      "volumen_m3": "<volumen_m3>",
      "aussenluft_m3_h": "<aussenluft_m3_h>",
      "ziel_frischluft_prozent": "<ziel_frischluft_prozent>"
    },
    "name": "luftwechsel_dauer_abschaetzen"
  }
}

Input Schema

NameRequiredDescriptionDefault
volumen_m3YesRaumvolumen in m³.
aussenluft_m3_hYesGemessener oder angenommener Außenluftstrom in m³/h. Umluft zählt nicht.
ziel_frischluft_prozentYesGewünschter Anteil ausgetauschter Ausgangsluft in Prozent.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuinely non-obvious behavioral context: the result is an estimate that assumes perfect mixing, which tells the agent the output is idealized rather than a measured value. It does not state the return unit or whether the estimate is conservative, which keeps it below a 5.

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?

A single sentence with the purpose front-loaded and no filler. The German/English duplication is slightly redundant but serves bilingual clarity and does not obscure the key 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?

This is a pure computation tool with three required parameters and no output schema, so the description carries the burden of explaining the result. It explains the model assumption but never says what is returned (a duration — in minutes? hours?) or how the result scales with the target percentage, leaving a real gap for an agent reporting the answer.

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 three parameters (including the 'Umluft zählt nicht' caveat and all min/max bounds) are already documented in the schema. The description restates the input quantities at a high level and adds no unit or format detail 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.

Purpose5/5

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

Names a specific verb (abschätzen/estimate) and resource (Lüftungsdauer) and states the two inputs it derives the answer from (Aussenluftstrom, Raumvolumen). The added physical model ('perfect mixing', 'target fresh-air fraction') makes it distinguishable from sibling calculators like geraetetakt_aus_messung or heizleistung_watt.

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 only implied via the precondition 'aus bekanntem Außenluftstrom und Raumvolumen' — i.e. you must already know the airflow. There is no explicit when-to-use/when-not guidance and no naming of an alternative for cases where airflow is unknown (e.g. a measurement or sizing tool).

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