Skip to main content
Glama

getecoback-climate-weather

tuerzugluft_abluft_an_aus_beobachtung

Read-only

Vergleicht Zugluftmeldungen im normalen Betrieb mit und ohne aktive mechanische Abluft bei gleicher Tür- und Fenstersituation. — Compare observed drafts during normal exhaust-on and exhaust-off periods with comparable door and window conditions.

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_aktiv": "<abluft_aktiv>",
      "abluft_inaktiv": "<abluft_inaktiv>",
      "gleiche_lage": "<gleiche_lage>"
    },
    "name": "tuerzugluft_abluft_an_aus_beobachtung"
  }
}

Input Schema

NameRequiredDescriptionDefault
abluft_aktivYesZugluft beobachtet während üblicher aktiver Abluft?
gleiche_lageYesTür, Fenster und äußere Bedingungen waren für beide Beobachtungen vergleichbar.
abluft_inaktivYesZugluft beobachtet während üblicher inaktiver Abluft?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/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 covered and the bar is lowered. The description adds the meaningful constraint that both observations must come from comparable door, window and ambient conditions during 'normal operation'. It does not say what happens when gleiche_lage is false or what form the comparison result takes.

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?

The comparison concept is front-loaded and clear, but the sentence is duplicated verbatim in German and English, doubling length without adding information. The bilingual pairing is defensible given the German tool name, but it makes the definition noticeably less tight than it could be.

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?

With three fully-documented parameters, a read-only annotation set and no output schema, the description covers the essential purpose and the comparability precondition. It is still silent on the outcome of the comparison (verdict, direction of effect) and on handling of inconclusive evidence, which an agent would need before interpreting a call.

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 the three parameters are already fully documented, and baseline is 3. The description adds only modest framing value by tying abluft_aktiv and abluft_inaktiv to 'normal operating' on/off periods; it adds no interpretation of the 'offen' enum value or of how a false gleiche_lage should be treated.

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 and resource: it compares draft observations taken during exhaust-on versus exhaust-off periods under comparable conditions. That is concrete enough to distinguish it from siblings that merely document a single draft location (e.g. tuerzugluft_unterkante_und_falz_getrennte_stellen). It does not, however, name or explicitly exclude any alternative tool.

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 rather than stated: the agent can infer the tool applies when observations exist from both an active and an inactive exhaust period with matched door/window conditions. There is no explicit when-to-use, when-not-to-use, or prerequisite guidance, and no alternative is named.

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