Skip to main content
Glama

getecoback-climate-weather

ventilator_sitzprobe_luftwechsel_tempstabil

Read-only

Trenne beobachtete Luftbewegung am Sitz von gleichzeitiger Raumtemperaturänderung — Separate seat-level airflow from measured room temperature changes

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": {
      "v_vor_m_s": "<v_vor_m_s>",
      "v_nach_m_s": "<v_nach_m_s>",
      "t_vor_c": "<t_vor_c>",
      "t_nach_c": "<t_nach_c>",
      "toleranz_c": "<toleranz_c>",
      "gleiche_ausrichtung": "<gleiche_ausrichtung>"
    },
    "name": "ventilator_sitzprobe_luftwechsel_tempstabil"
  }
}

Input Schema

NameRequiredDescriptionDefault
t_vor_cYesErste gleichzeitige Raumtemperatur am gleichen Ort
t_nach_cYesZweite gleichzeitige Raumtemperatur
v_vor_m_sYesAm Sitz vor dem Standortwechsel erfasste Luftgeschwindigkeit
toleranz_cYesGewählte Toleranz der Temperaturdifferenz
v_nach_m_sYesAm Sitz nach dem Wechsel, gleiches Verfahren
gleiche_ausrichtungYesAnemometer in gleicher Ausrichtung, Gerätestufe und Sensorhöhe gleich

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/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 and the description need only add behavioral context. It adds the notion that two effects are being disentangled, which is helpful, but says nothing about the result form (a verdict, a residual velocity, a boolean) or what happens when gleiche_ausrichtung is false or the tolerance is exceeded.

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?

The definition is short and front-loaded, but it is presented twice in German and English, which doubles length without adding information. The single semantic sentence is efficient, but the bilingual duplication and lack of any structural follow-up on the operation keep it at adequate.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a six-parameter computation with no output schema, so the description is the only place an agent could learn what the tool returns or how the tolerance drives the decision. It supplies only the high-level intent and leaves the result semantics and failure conditions unstated, which is a real gap for a no-output-schema tool.

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 one of the six parameters is already documented with units, ranges, and meaning. The description adds no interpretation of toleranz_c, of how the before/after pairs are compared, or of why orientation equality matters, so it sits at the baseline for a fully documented 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 states a specific analytical operation: separating observed seat-level airflow from a concurrent room-temperature change. That is more than a restatement of the tool name and lets an agent recognize it as a measurement-discrimination step rather than another ventilator configuration helper. It stops short of specifying the method or outcome, so it is clear but not fully differentiating.

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 guidance on when to run this analysis, what preconditions must hold (e.g. the two readings must be truly simultaneous), or how it relates to sibling measurement tools such as the direct-wind control check. The agent must infer usage entirely from the parameter names.

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