Skip to main content
Glama

getecoback-climate-weather

luftkuehler_luftgeschwindigkeit_kopf_und_tischzone

Read-only

Vergleicht eine räumliche Zielverteilung des Luftstroms zwischen Sitzhöhe und Tischhöhe — Check a two-zone airflow arrangement against distinct personal goals.

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": {
      "oben": "<oben>",
      "unten": "<unten>",
      "sitz_min": "<sitz_min>",
      "tisch_max": "<tisch_max>",
      "gleicher_zustand": "<gleicher_zustand>"
    },
    "name": "luftkuehler_luftgeschwindigkeit_kopf_und_tischzone"
  }
}

Input Schema

NameRequiredDescriptionDefault
obenYesBeobachtete Luftbewegung am Sitzplatz in m/s.
untenYesBeobachtete Luftbewegung auf gleicher Achse am Tisch in m/s.
sitz_minYesEigener gewünschter Mindestwert am Sitzplatz in m/s.
tisch_maxYesEigener gewünschter Höchstwert am Tisch in m/s.
gleicher_zustandYesGleiche Einstellung und zur selben Ausrichtung gehörende Messungen?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/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 agent knows this is a safe, local, non-mutating check; the description adds that the comparison is per-zone against individual targets. It does not say what the result looks like (pass/fail per zone, deviation, both), which matters because there is no output schema, though the closed-world annotation removes most environmental uncertainty.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded and short, stating the comparison first. However, the English half largely restates the German half ('räumliche Zielverteilung' versus 'distinct personal goals') without adding new information, so one of the two clauses does not fully earn its place.

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 five required parameters, no output schema, and a read-only annotation profile, the definition is adequate but leaves the return value undefined. An agent can construct the call correctly but cannot anticipate whether the response is a verdict, per-zone deltas, or a list of violations, which is the main remaining gap.

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 every parameter carries units (m/s) and a documented meaning, so the description adds only framing (two-zone, personal target min at seat versus max at table) rather than new parameter semantics. Baseline 3 is appropriate since the schema does the heavy lifting, including the 'gleicher_zustand' comparability condition.

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?

States a concrete operation on a concrete resource: it compares ('Vergleicht') a spatial airflow target distribution between seating height and table height. It is specific enough to distinguish from sibling tank/moisture tools, but it never names an alternative tool, so differentiation relies on the reader inferring it from the resource wording.

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 'Check a two-zone airflow arrangement against distinct personal goals' implies the use case (comparing measured seat/table airflow against the user's own min/max targets), but there is no explicit when-to-use versus when-not-to-use guidance and no stated prerequisite such as requiring measurements from the same orientation.

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