Skip to main content
Glama

getecoback-climate-weather

querlueften_richtungskarte_beobachten

Read-only

Luftbewegung an zwei Öffnungen und dazwischen mit einem frei gehaltenen Papierstreifen protokollieren — Map observed flow directions without estimating an air exchange rate.

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": {
      "oeffnung_a": "<oeffnung_a>",
      "innen": "<innen>",
      "oeffnung_b": "<oeffnung_b>",
      "gleichzeitig": "<gleichzeitig>"
    },
    "name": "querlueften_richtungskarte_beobachten"
  }
}

Input Schema

NameRequiredDescriptionDefault
innenYesBeobachtung ungefähr mittig auf der vermuteten Strecke.
oeffnung_aYesBeobachtung in der ersten Öffnung bezogen auf den Raum.
oeffnung_bYesBeobachtung in der zweiten Öffnung bezogen auf den Raum.
gleichzeitigYesZeitnah bei unveränderter Stellung von Türen und Fenstern beobachtet?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/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 safety is covered. The description adds the observation method (paper strip at two openings and between) and an important scope boundary (no air-exchange-rate estimation), but it does not describe what the tool returns or how the record is persisted.

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 front-loaded sentence conveys purpose, method, and exclusion without filler. The German/English bilingual form is slightly redundant but clarifies intent efficiently; minor deduction for repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 4-parameter observation-logging tool with full schema coverage and clear annotations, the description covers purpose, method, and a key exclusion. It leaves the return/persistence behavior unstated, which is a moderate gap given there is no output schema, but the 'map observed flow directions' phrasing implies the result.

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%, so the schema already documents all four parameters including the three enums. The description adds some context by locating observations at two openings and between, but it does not explain the enum values or the simultaneity parameter beyond what the schema provides; 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?

The description states a specific action: recording air movement at two openings and in between using a hand-held paper strip, and mapping observed flow directions. It distinguishes itself from rate-estimation tools with 'without estimating an air exchange rate', though it does not name a specific sibling.

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?

It implies the tool is for mapping observed flow directions and explicitly excludes estimating an air exchange rate, providing a negative scope boundary. However, it does not give positive when-to-use conditions or name alternative observation/protocol tools, leaving selection largely inferential.

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