Skip to main content
Glama

getecoback-raumklima

nachtlueftung_luftpfad_rueckstrom_probe

Read-only

Luftwegrichtung an zwei Öffnungen und einem Innenübergang gemeinsam beobachten — Flag incomplete cross-ventilation-path evidence.

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": {
      "aussen_a": "<aussen_a>",
      "innen_uebergang": "<innen_uebergang>",
      "aussen_b": "<aussen_b>",
      "gleiche_phase": "<gleiche_phase>"
    },
    "name": "nachtlueftung_luftpfad_rueckstrom_probe"
  }
}

Input Schema

NameRequiredDescriptionDefault
aussen_aYesAn Öffnung A beobachtet.
aussen_bYesAn Öffnung B beobachtet.
gleiche_phaseYesAlle drei Beobachtungen in derselben Wetter- und Fensterphase gemacht?
innen_uebergangYesAm Innenübergang beobachtet.

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 one behavioral fact beyond that — the tool flags incomplete evidence rather than just recording observations — but does not say what counts as incomplete or how the flag is surfaced. Adequate but thin for a tool whose whole point is a judgment output.

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 with no padding; the core action comes first and the flagging clause follows. Slightly penalized because the compressed phrasing makes the second half harder to parse than it needs to 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 four required parameters, three of them enums, no output schema, and light annotations, the definition covers the input side adequately. It leaves an agent guessing about the return shape — what an 'incomplete evidence' flag looks like and whether it accompanies the raw observations — which matters given there is no 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 enums for the three observation points are fully documented, so the schema carries the parameter burden. The description only restates the two-openings-plus-interior-transition structure and adds nothing about value semantics or how 'unklar'/'wechselnd' interact with the completeness flag. 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 names a concrete verb and object: observe air-path direction at two openings plus one interior transition, and flag incomplete cross-ventilation evidence. That maps one-to-one onto the three measurement parameters and is distinguishable from sibling probes. It stops short of a 5 because 'Flag incomplete cross-ventilation-path evidence' is cryptic about what is actually produced.

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 word 'gemeinsam' (jointly) plus the required same-phase parameter imply these three observations must be taken together, which is usable guidance. However, there is no statement of when to pick this tool over related night-ventilation or air-path tools, and no exclusions or prerequisites are given.

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