Skip to main content
Glama

getecoback-climate-weather

lueftung_aussenluft_umluftrate_aufteilen

Read-only

Trennt dokumentierte Außenluft und Umluft eines gemischten Zuluftstroms — Split a specified supply flow into outdoor air and recirculation.

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": {
      "zuluft_m3h": "<zuluft_m3h>",
      "aussenanteil_prozent": "<aussenanteil_prozent>",
      "betriebsmin": "<betriebsmin>"
    },
    "name": "lueftung_aussenluft_umluftrate_aufteilen"
  }
}

Input Schema

NameRequiredDescriptionDefault
zuluft_m3hYesGesamter dokumentierter Zuluftstrom im betrachteten Modus in m³/h.
betriebsminYesLaufzeit dieses Modus in Minuten.
aussenanteil_prozentYesDokumentierter Außenluftanteil desselben Modus in Prozent.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/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 safe, purely computational, offline operation; the description adds only that the split is of a 'documented' mixed flow. It says nothing about the result — no indication of what quantities come back (outdoor m³/h, recirculation m³/h, share), no rounding or edge-case behaviour at 0% or 100% outdoor air.

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 compact sentence with the object of the operation front-loaded, plus a bilingual restatement that aids comprehension. The German and English halves are near-duplicates, which is slight redundancy, but nothing is wasted beyond that.

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?

All three inputs are well documented and the safety profile is covered by annotations, so the definition is close to sufficient. However, with no output schema present, the description should describe what the split yields and is silent on it — the main remaining gap for an agent deciding whether this tool returns what it needs.

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%, with all three parameters (zuluft_m3h, aussenanteil_prozent, betriebsmin) fully documented including units and ranges. The description's phrasing of 'documented outdoor air and recirculation of a mixed supply flow' restates the same concept without adding format, tolerance or consistency constraints beyond the schema, so this is the baseline 3.

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?

States a specific verb (trennt/split) and a specific resource (a mixed supply air flow into outdoor air and recirculation), which is enough to distinguish it from the neighbouring ventilation tools like co2_abklingtest or belegungswechsel_zeitfenster. It stops short of naming any sibling outright, so the differentiation is inferred rather than declared.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance and no alternative is offered. The adjective 'dokumentierte' plus 'eines gemischten Zuluftstroms' weakly implies the tool only applies to documented (not measured) values of a single mixed mode, but that precondition is never spelled out as guidance.

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