Skip to main content
Glama

getecoback-raumklima

luftreiniger_stellort_luftstrom_sichtprobe

Read-only

Vergleicht den gemessenen Ausblasstrom an zwei Stellorten, ohne Filter oder Stufe zu wechseln — Compare outlet airspeed after moving an intact purifier.

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": {
      "vorher_m_s": "<vorher_m_s>",
      "nachher_m_s": "<nachher_m_s>",
      "vergleichbare_messung": "<vergleichbare_messung>"
    },
    "name": "luftreiniger_stellort_luftstrom_sichtprobe"
  }
}

Input Schema

NameRequiredDescriptionDefault
vorher_m_sYesAusblasgeschwindigkeit am ersten Ort in m/s.
nachher_m_sYesAusblasgeschwindigkeit am zweiten Ort in m/s.
vergleichbare_messungYesGleiche Stufe, Filter, Messdistanz und Sensorwinkel?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/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 the device must be intact and the filter/stage unchanged, but says nothing about what the comparison yields (e.g., whether a verdict or just a delta is returned) or about measurement validity limits.

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 with the key constraint front-loaded, followed by an English rendering. The bilingual duplication is mild redundancy but aids clarity for a German-named tool; nothing else is wasted.

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

Completeness4/5

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

For a simple read-only two-value comparison with three fully described parameters and no output schema, the description covers the essential preconditions. Only the nature of the returned comparison result remains unspecified, which is a minor gap at this complexity.

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 three parameters are already documented in the schema, giving a baseline of 3. The description reinforces that the two readings must belong to the same configuration, which maps onto vergleichbare_messung but adds no new semantics for vorher_m_s/nachher_m_s.

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 and resource: comparing measured outlet airspeed (Ausblasstrom) at two locations, with the qualifier that the purifier is intact and no filter or stage change occurs. That is enough to distinguish it from the filter-change sibling, though it does not explicitly name an alternative tool.

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 implied rather than stated: you use it after moving the unit, keeping filter and stage constant. There is no explicit when-not guidance and no sibling tool is named as an alternative for other comparison scenarios, so the agent must infer the boundary.

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