Skip to main content
Glama

getecoback-raumklima

lueftung_oeffnungsstufen_durchzug_grenze

Read-only

Vergleicht zwei Fensteröffnungen mit einer persönlich gesetzten Zugluftgrenze — Compare two opening positions against a user-set local airspeed limit.

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_m_s": "<oeffnung_a_m_s>",
      "oeffnung_b_m_s": "<oeffnung_b_m_s>",
      "persoenliche_grenze_m_s": "<persoenliche_grenze_m_s>",
      "versuche_vergleichbar": "<versuche_vergleichbar>"
    },
    "name": "lueftung_oeffnungsstufen_durchzug_grenze"
  }
}

Input Schema

NameRequiredDescriptionDefault
oeffnung_a_m_sYesHöchster beobachteter Messwert am gleichen Aufenthaltsort bei Stellung A in m/s.
oeffnung_b_m_sYesHöchster beobachteter Messwert am gleichen Aufenthaltsort bei Stellung B in m/s.
versuche_vergleichbarYesWaren Position, Messdauer und Wetter bei beiden Versuchen vergleichbar?
persoenliche_grenze_m_sYesSelbst gewählte Vergleichsgrenze am Aufenthaltsort in m/s.

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?

The annotations already declare readOnlyHint=true and openWorldHint=false, so the safe, local-read nature is covered. The description adds that the limit is self-chosen and measured at the user's location, but it does not say how the boolean 'versuche_vergleichbar' changes behavior — e.g. whether an incomparable trial blocks the comparison or only warns.

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 a single compact sentence pair with the core action front-loaded. The German and English render the same content, which is slight duplication but keeps the tool readable for mixed-language agents.

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 no output schema, the description never indicates what the comparison returns (a verdict, a delta, a recommendation), leaving the agent unable to anticipate the result. Parameters and safety are adequately covered by schema and annotations, so the gap is narrow but real.

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%, so every parameter is already documented in detail, including units and the 'höchster beobachteter Messwert' semantics. The description only restates the user-set limit concept and adds no format, default, or edge-case guidance beyond the schema, making the baseline 3 appropriate.

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 specific verb ('Vergleicht') and resource ('zwei Fensteröffnungen') and states the comparison target, a user-set airspeed limit. It is clear enough to distinguish from unrelated siblings such as repair-price or CO2-decay tools, though it does not explicitly contrast with the closest ventilation-comparison siblings.

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 'Vergleicht' and the phrase 'gegen eine persönlich gesetzte Zugluftgrenze' imply the comparison scenario, but there is no explicit statement of when to choose this tool over alternatives, nor any prerequisite or exclusion. Usage is inferable rather than stated.

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