Skip to main content
Glama

getecoback-raumklima

nachtlueftung_querweg_wiederholte_richtungswechsel

Read-only

Prüfe, ob eine Richtung am geöffneten Durchgang beständig blieb oder innerhalb der Stichproben wechselte — Count directional reversals in repeated doorway airflow checks

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": {
      "a": "<a>",
      "b": "<b>",
      "c": "<c>",
      "oeffnungen_unveraendert": "<oeffnungen_unveraendert>"
    },
    "name": "nachtlueftung_querweg_wiederholte_richtungswechsel"
  }
}

Input Schema

NameRequiredDescriptionDefault
aYesHandbeobachtung zuerst am gleichen Punkt
bYesZweite Beobachtung
cYesDritte Beobachtung
oeffnungen_unveraendertYesGeöffnete Fenster, Tür und Prüfort zwischen den Beobachtungen unverändert

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already establish readOnlyHint=true and openWorldHint=false, and the description is consistent with a non-mutating analytical check. It adds that the tool compares direction across repeated samples and counts reversals, though it does not explain how 'unklar' observations affect the count or the exact return shape.

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?

It is a single front-loaded sentence and the core test is stated immediately. The dash adds an English restatement of the same idea, which is mildly redundant but not enough to obscure the purpose.

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 four-parameter read-only check with full schema coverage and no output schema, the description supplies the key purpose and says the result is a count of reversals. It leaves some interpretation details implicit, such as how 'unklar' affects the count, but not enough to block correct invocation.

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 a, b, c and oeffnungen_unveraendert are already documented, including enums and the unchanged-openings precondition. The description reinforces that a/b/c are repeated samples but does not add mapping or special handling beyond the schema, so baseline 3 applies.

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 gives a specific verb (check/count) and object (directional reversals in repeated doorway airflow observations) and states the condition it tests: whether direction stayed constant or changed across samples. It is clear on its own, though it does not explicitly distinguish itself from the many sibling night-ventilation probes.

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 phrase 'in repeated doorway airflow checks' implies the scenario for use: when several repeated direction observations exist. It does not state when not to use it or name an alternative sibling for related airflow tests, so guidance remains implicit.

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