Skip to main content
Glama

getecoback-raumklima

lueftungsangebot_zuluft_abluft_doppelt_gezaehlt

Read-only

Prüft ob ein Summenwert Zu- und Abluft als gemeinsamen Außenluftbedarf doppelt zählen würde — Keep simultaneous supply and extract readings separate from an advertised volume sum.

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>",
      "abluft_m3h": "<abluft_m3h>",
      "gleicher_fall": "<gleicher_fall>"
    },
    "name": "lueftungsangebot_zuluft_abluft_doppelt_gezaehlt"
  }
}

Input Schema

NameRequiredDescriptionDefault
abluft_m3hYesSeparat erfasster Abluftstrom im selben Fall in m³/h.
zuluft_m3hYesSeparat als Außen-Zuluft nachgewiesener Volumenstrom in m³/h.
gleicher_fallYesBeide Angaben sind zeitgleich, gleiche Gebäudegrenze und mit getrennten Strömen belegt?

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 only declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds the domain rule being tested (double counting of supply/extract as shared outdoor air demand) but says nothing about the returned verdict, thresholds, or how borderline cases are handled.

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?

Two compact sentences, front-loaded with the German purpose and followed by an English restatement of the same rule. Slightly redundant by being bilingual, but no filler.

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 three-parameter read-only check the definition is serviceable, especially since the schema carries full parameter documentation and no output schema exists. However, it does not describe what the result communicates, leaving the agent to guess the response shape.

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 are already documented, including units and the 'gleicher Fall' simultaneity condition. The description reinforces the concept behind abluft/zuluft but adds no syntax, format, or edge-case meaning beyond the schema.

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 specific check ('Prüft ob ein Summenwert ... doppelt zählen würde') and clarifies the concept with the English sentence about keeping simultaneous supply and extract readings separate. It is a clear verb+resource statement, though it does not explicitly name or distinguish itself from sibling tools such as other Lüftungsangebot checks.

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: apply it when a supply and extract reading might both be counted against one advertised volume sum. There is no explicit when-not guidance or named alternative, so the agent must infer the triggering situation from the wording.

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