Skip to main content
Glama

getecoback-raumklima

lueftungsrichtung_intervallanteile

Read-only

Verdichtet wiederholte Richtungsbeobachtungen zu Zeitanteilen für eine Öffnung — Summarize equal-length airflow direction observations for an opening.

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": {
      "einwaerts": "<einwaerts>",
      "auswaerts": "<auswaerts>",
      "wechselnd_oder_unklar": "<wechselnd_oder_unklar>"
    },
    "name": "lueftungsrichtung_intervallanteile"
  }
}

Input Schema

NameRequiredDescriptionDefault
auswaertsYesAnzahl gleich langer Intervalle mit beobachtetem Auswärtsstrom.
einwaertsYesAnzahl gleich langer Intervalle mit beobachtetem Einwärtsstrom.
wechselnd_oder_unklarYesAnzahl gleich langer Intervalle mit Wechsel oder unklarem Befund.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds that repeated observations are condensed into time shares, but it does not explain output shape, normalization, handling of a zero total, or assumptions about interval length.

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 one compact bilingual sentence with the verb and resource front-loaded and no extraneous explanation. The German and English versions duplicate the same content, but the duplication is brief and controlled.

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?

This is a simple read-only three-parameter calculation, and the annotations plus schema cover its structure. The description identifies the output as time shares, but without an output schema it does not specify the returned proportions or edge-case behavior.

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%, and the schema already defines all three required counts, including the equal-length interval framing. The description repeats the equal-length observation concept but provides no additional per-parameter meaning beyond the schema.

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 uses a specific verb, 'Verdichtet' / 'Summarize', and a specific resource, repeated airflow direction observations for an opening, producing time shares. It is clear what the tool does, but it does not explicitly distinguish this operation from any sibling tool or name an alternative.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use, when-not-to-use, prerequisite, or alternative guidance. The operation itself implies that the tool applies when repeated equal-length direction observations exist, but that usage context is only inferred.

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