Skip to main content
Glama

getecoback-climate-weather

klima_abluftrichtung_fassadenbeobachtung

Read-only

Offene Fenster, Türen und Ansaugöffnungen im beobachteten Abluftweg dokumentieren — Identify nearby openings to record when outdoor exhaust may be reaching them.

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": {
      "auslass_pfadrichtung": "<auslass_pfadrichtung>",
      "rueckstrom_beobachtet": "<rueckstrom_beobachtet>",
      "aufstellort_dokumentiert": "<aufstellort_dokumentiert>"
    },
    "name": "klima_abluftrichtung_fassadenbeobachtung"
  }
}

Input Schema

NameRequiredDescriptionDefault
auslass_pfadrichtungYesBeobachtung unmittelbar vor dem vorgesehenen Auslass.
rueckstrom_beobachtetYesAm eigenen Fenster tritt beobachtbar warme Abluft wieder ein?
aufstellort_dokumentiertYesGerätemodell und Auslassposition sind für die Beobachtung erfasst?

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 covered. The description adds that the output is a documented observation of openings along the exhaust path, but it says nothing about what the tool produces, whether observations persist, or how the enum classification affects behavior.

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?

The definition is short and front-loads the concrete objects to document before the situational clause. The English half largely restates the German half, which is mild redundancy but keeps the tool usable for either language.

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, fully documented, read-only assessment tool this is adequate, and the description usefully clarifies the intent behind an otherwise opaque German name. It remains unclear what the assessment returns or how the recorded openings are used, a gap not filled by any output schema.

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 coverage is 100%, and the property descriptions are already detailed and phrased as observation questions, so the schema carries the parameter burden. The description's mention of windows, doors and intake openings only loosely maps onto the enum value 'zu_gebaeudeoeffnung' and the Rückstrom boolean, adding little beyond the structured data.

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 object: recording open windows, doors and intake openings along the observed exhaust path, so an agent knows this is an observation/documentation tool rather than a measurement or calculation tool. It does not, however, distinguish itself from close siblings such as klima_abluftweg_pruefen or klima_zu_und_rueckluft_messen by naming when one is preferred over the other.

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?

The clause 'when outdoor exhaust may be reaching them' implies the situation in which the tool applies, which is useful context. There are no explicit exclusions, prerequisites or named alternatives, so the agent must infer the boundary against the many related klima_* tools.

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