Skip to main content
Glama

getecoback-raumklima

ventilator_platzbedarf_pruefen

Read-only

Standfuß und Schwenkbreite mit dem verfügbaren Stellplatz abgleichen — Check a fan base and oscillation envelope before buying.

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": {
      "stellbreite_cm": "<stellbreite_cm>",
      "stelltiefe_cm": "<stelltiefe_cm>",
      "breite_betrieb_cm": "<breite_betrieb_cm>",
      "tiefe_betrieb_cm": "<tiefe_betrieb_cm>",
      "freiraum_je_seite_cm": "<freiraum_je_seite_cm>"
    },
    "name": "ventilator_platzbedarf_pruefen"
  }
}

Input Schema

NameRequiredDescriptionDefault
stelltiefe_cmYesFrei verfügbare Tiefe am geplanten Stellplatz in cm.
stellbreite_cmYesFrei verfügbare Breite am geplanten Stellplatz in cm.
tiefe_betrieb_cmYesMaximale Gerätetiefe im Betrieb in cm.
breite_betrieb_cmYesMaximale Gerätebreite im Betrieb einschließlich Schwenkbereich in cm.
freiraum_je_seite_cmYesZusätzlicher freier Rand je Seite gemäß Anleitung in cm.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The annotations already establish that this is a read-only, closed-world check, so the description does not need to disclose safety behavior. It adds useful context that the check compares the stand base and oscillation envelope against available space. However, it does not explain what the check returns, whether thresholds are pass/fail, or how clearance is interpreted.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single front-loaded sentence in German with an English clarifier, and every phrase earns its place. It states the comparison subject, the reference quantity, and the timing without waste or repetition.

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?

With five fully described required parameters and clear read-only annotations, the definition gives enough context to select and invoke the tool. The remaining gap is that it never describes the nature of the result, such as whether it returns a simple fit verdict or detailed clearance measurements. For a low-complexity check without an output schema, this is nearly complete.

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 are already documented in the input schema. The description uses terms like 'Standfuß' and 'Schwenkbreite' that correspond to the schema fields, but it adds no additional parameter-level meaning such as units, measurement conventions, or tolerance behavior beyond the schema. A baseline 3 is appropriate.

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 comparison task: matching a fan base and swivel/oscillation width against available floor space before purchase. The verb 'abgleichen' and the explicit buying context make the purpose clear without relying on the tool name alone. It does not explicitly differentiate itself from sibling tools, but the task is distinctive.

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 phrase 'before buying' gives clear usage context: this is a pre-purchase fit check for a fan. It does not state when not to use the tool or name any alternative sibling tool, but the situational guidance is strong enough for correct selection.

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