Skip to main content
Glama

getecoback-raumklima

ventilator_schwenkbereich_sitzplaetze

Read-only

Die gemessenen Seitenwinkel zweier Sitzplätze mit dem beobachteten Schwenkweg vergleichen — Check whether an observed fan sweep geometrically reaches both chosen seats.

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": {
      "links_grad": "<links_grad>",
      "rechts_grad": "<rechts_grad>",
      "platz_a_grad": "<platz_a_grad>",
      "platz_b_grad": "<platz_b_grad>"
    },
    "name": "ventilator_schwenkbereich_sitzplaetze"
  }
}

Input Schema

NameRequiredDescriptionDefault
links_gradYesBeobachtete linke Grenze von der Mitte in Grad.
rechts_gradYesBeobachtete rechte Grenze von der Mitte in Grad.
platz_a_gradYesGemessene Richtung von Sitz A, links negativ und rechts positiv.
platz_b_gradYesGemessene Richtung von Sitz B auf derselben Achse.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3/5.0
Behavior2/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 only needs to add behavioural depth. It adds none: it does not say whether the check is a strict containment test, how boundary cases (a seat exactly on the sweep edge) are treated, whether the left/right limits are assumed symmetric, or what the caller receives back. With no output schema, that omission matters.

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 core statement is a single tight sentence, but it is then repeated verbatim in English after an em dash, so the same content occupies twice the space without adding information. Front-loading is fine; the bilingual duplication is the main waste.

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 pure computation/check tool with four required numeric parameters and no output schema, so the description carries the burden of explaining what a caller gets back and how to read it. It says nothing about the result (boolean verdict, residual margin, failure reason) or about tolerances, leaving a material gap for the tool's primary consumer.

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 the four parameters and their ranges are fully documented in the schema and the baseline is 3. The description adds a little framing by pairing the observed sweep (links/rechts) with the two measured seat directions, but it contributes no format, sign-convention, or edge-case detail beyond what the schema already states.

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 gives a specific verb and resource: it compares measured side angles of two seats against an observed sweep and checks whether the sweep geometrically reaches both. That is far more than a restatement of the name. It does not, however, contrast itself with neighbouring geometry helpers such as ventilator_platzbedarf_pruefen or dachfenster_schwenkraum_rechnen, so an agent must infer the distinction.

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 the stated purpose — you call it when you want to know whether a fan sweep covers two given seat positions. There is no explicit when-to-use/when-not, no prerequisites, and no pointer to an alternative tool for a different geometric question. Adequate but leaves routing decisions to inference.

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