Skip to main content
Glama

getecoback-raumklima

arbeitsplatz_luefter_probe_luftwert_und_empfinden

Read-only

Wenn am Schreibtisch ein Luftstrom als kühler erlebt wird, die lokale Luftmessung getrennt von der persönlichen Rückmeldung prüfen — Report whether desk fan comfort moved independently of measured air temperature.

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_luft_c": "<vorher_luft_c>",
      "nachher_luft_c": "<nachher_luft_c>",
      "messband_k": "<messband_k>",
      "persoenlich_kuehler": "<persoenlich_kuehler>",
      "probe_vergleichbar": "<probe_vergleichbar>"
    },
    "name": "arbeitsplatz_luefter_probe_luftwert_und_empfinden"
  }
}

Input Schema

NameRequiredDescriptionDefault
messband_kYesAbgeleitete eigene Grenze der Luftvergleichsmessung in K.
vorher_luft_cYesEigener Messwert auf derselben Höhe vor der Luftstromprobe.
nachher_luft_cYesLuftmesswert bei der Beobachtung am gleichen Messpunkt.
probe_vergleichbarYesArbeitsplatz, Aufgabe, Kleidung und direkter Sonneneinfall blieben vergleichbar.
persoenlich_kuehlerYesDie Person berichtete bei derselben Aufgabe ein kühleres Gefühl.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/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 evaluation. The description adds the intent of the probe but says nothing further about behavior: no indication of how the comparison is judged, what happens when probe_vergleichbar is false, or how messband_k gates the outcome. With annotations carrying the safety profile, this is adequate but thin.

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 trigger condition is front-loaded in the first clause and the reporting goal follows immediately, with no padding. The German and English halves restate the same premise, which costs a little length but improves discoverability across languages.

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 read-only five-parameter probe with fully documented schema fields and no output schema, the definition gives an agent enough to decide when to call it and what the call represents. The remaining gap is how the verdict is derived from messband_k and the before/after deltas, which the agent must infer from the parameter descriptions.

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 five parameters (vorher_luft_c, nachher_luft_c, messband_k, persoenlich_kuehler, probe_vergleichbar) already carry their own explanatory text and the description need not repeat it. The description contributes only the overall framing of separating measurement from perception, which maps loosely onto the kuehler/vergleichbar flags without adding syntax or semantics 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-and-resource pairing: separate the local air measurement from the personal feedback and report whether desk-fan comfort moved independently of measured air temperature. That is concrete enough to distinguish it from a plain temperature-logging sibling. It does not, however, name or contrast itself against the closely related tischluefter/messabdeckung or sitzdauer_waermerueckmeldung siblings, so the differentiation is left to the agent's inference.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The opening conditional ('Wenn am Schreibtisch ein Luftstrom als kühler erlebt wird') supplies an explicit trigger for when to reach for this probe rather than a general measurement tool. What is missing is any when-not guidance or a named alternative for cases where the two signals are not meant to be separated.

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