Skip to main content
Glama

getecoback-climate-weather

lueftungsangebot_abluftschlauch_frischluftweg_beleg

Read-only

Prüft ob für ein mobiles Angebot außer einem Abluftweg auch ein eigener Außenluft-Zuluftweg belegt ist — Verify an actual outdoor-air supply path independently of an exhaust hose.

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": {
      "abluft": "<abluft>",
      "frischweg": "<frischweg>",
      "fuer_raumnutzung": "<fuer_raumnutzung>"
    },
    "name": "lueftungsangebot_abluftschlauch_frischluftweg_beleg"
  }
}

Input Schema

NameRequiredDescriptionDefault
abluftYesAbtransport nach außen beschrieben.
frischwegYesEigener, als Außenluftzufuhr belegter Weg.
fuer_raumnutzungYesGehört der bestätigte Zuluftweg laut Unterlage zum betrachteten Betriebsmodus?

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 safety profile is clear and the description does not contradict it — the verification framing is consistent. The description adds the conceptual distinction it checks (independence of the supply path from the exhaust path via 'unabhängig von einem Abluftschlauch'), but says nothing about the outcome shape or what happens when inputs are inconsistent.

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 statement of the check. The English half is a near-restatement rather than added information, so there is some redundancy, but nothing is padded or buried.

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-boolean/enum read-only check with full schema coverage, the description covers the what but not the result: with no output schema present, the agent cannot tell whether the tool returns a verdict, a list of findings, or an error on contradiction. The interaction between fuer_raumnutzung and the overall verdict is also left unexplained.

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%, and all three parameters carry their own descriptions plus an enum for frischweg, so the schema does the heavy lifting. The description's wording ('Außenluft-Zuluftweg' vs 'Abluftweg') loosely mirrors the abluft/frischweg parameters but adds no format, dependency, or cross-parameter semantics beyond the schema. Baseline 3 is appropriate.

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 states a specific verb (Prüft/Verify) and a precise resource: whether a dedicated outdoor-air supply path (eigener Außenluft-Zuluftweg) is documented independently of an exhaust hose for a mobile offer. This is much more specific than the tool name alone. It does not, however, name or distinguish itself from the many similarly named '..._beleg' siblings, which all perform documentary-evidence 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 only implied through the scoping phrase 'für ein mobiles Angebot' — the agent can infer this applies to mobile-unit offers with an exhaust hose. There is no explicit when-to-use/when-not-to-use statement and no alternative tool is named, even though siblings like lueftungsangebot_zuluft_abluft_doppelt_gezaehlt could plausibly overlap.

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