Skip to main content
Glama

getecoback-raumklima

tueroeffnung_luftschichtung_drei_hoehen

Read-only

Hält gegensätzliche Luftströmung über drei Höhen einer Türöffnung fest — Record opposing doorway flow observations at three relative heights.

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": {
      "unten": "<unten>",
      "mitte": "<mitte>",
      "oben": "<oben>"
    },
    "name": "tueroeffnung_luftschichtung_drei_hoehen"
  }
}

Input Schema

NameRequiredDescriptionDefault
obenYesBeobachtung nahe Türoberkante.
mitteYesBeobachtung auf mittlerer Höhe.
untenYesBeobachtung nahe Türunterkante.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/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 bar is lower. The word 'festhalten/Record' might superficially suggest persistence, but in the context of a read-only tool it reads as capturing an observation rather than mutating state, so this is at most mild and not a contradiction. The description adds nothing about how the observation is validated, stored, or returned.

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?

A single bilingual sentence with the operational content front-loaded and no filler. The German/English duplication costs a few tokens but serves as harmless disambiguation rather than padding.

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?

This is a simple tool with three required enum parameters, an explicit annotation profile, and no output schema to explain. Given that, the description is essentially sufficient for correct invocation, with only the absence of usage routing being a mild 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 each of the three parameters has an enum with a clear German description tying it to a height. The description's phrase 'over three heights' echoes the schema without adding semantics, so the baseline of 3 applies.

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 object ('Record opposing doorway flow observations at three relative heights'), which tells the agent exactly what is being captured. The only weakness is that it does not distinguish itself from any named sibling, though the specific domain phrasing already narrows the space considerably.

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 when-to-use guidance, no exclusions, and no reference to an alternative tool. The agent must infer the applicable scenario (a doorway flow measurement with stratified flow) purely from the term 'opposing doorway flow'.

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