Skip to main content
Glama

getecoback-raumklima

schlafplatz_luftstrom_messen

Read-only

Luftgeschwindigkeit am Schlafplatz vor und nach Umstellen des Geräts vergleichen — Compare measured bed-level air speed after changing airflow direction.

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": {
      "zuvor_m_s": "<zuvor_m_s>",
      "danach_m_s": "<danach_m_s>",
      "einzel_fehler_m_s": "<einzel_fehler_m_s>",
      "gleicher_modus": "<gleicher_modus>"
    },
    "name": "schlafplatz_luftstrom_messen"
  }
}

Input Schema

NameRequiredDescriptionDefault
zuvor_m_sYesGemittelte Luftgeschwindigkeit am selben Schlafplatz in m/s vor der Änderung.
danach_m_sYesGemittelte Luftgeschwindigkeit dort nach der Änderung in m/s.
gleicher_modusYesGleiche Lüfterstufe, Fensterstellungen, Messposition und ausreichend lange Messdauer?
einzel_fehler_m_sYesAbsoluter Toleranzbetrag pro Messung 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?

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds that this is a comparative evaluation of two measurements rather than a raw reading, but it never says what the comparison produces (delta, verdict, pass/fail) or what happens when gleicher_modus is false — a meaningful gap for a tool whose whole point is a validity-gated comparison.

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?

Two short sentences, front-loaded with the comparison intent. The German and English halves largely restate each other, which is mild redundancy but keeps the definition compact.

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, no output schema, and only read-only annotations, the description should say more about the result of the comparison and how the same-mode gate affects it. It is adequate to select the tool but leaves the agent guessing about the return value.

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 all four parameters are already documented in the schema, including the tolerance and the same-mode validity gate. The description only restates the before/after framing and adds no syntax, units, or interpretation guidance 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 names a specific verb (compare) and a specific resource (bed-level air speed at the sleeping place, before vs. after repositioning the device). That scope distinguishes it from siblings such as luftreiniger_filterwechsel_luftstrom, though no sibling is named explicitly.

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?

Usage is only implied by 'vor und nach Umstellen des Geräts' — the agent can infer this is a before/after comparison after a device change. There is no explicit when-to-use, when-not-to-use, or pointer to an alternative tool for a plain single-point air-speed reading.

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