Skip to main content
Glama

getecoback-raumklima

vorhang_parkbreite_fensterweg

Read-only

Aus gemessenem Stoffpaket und Bedienweg die offene Fensterbreite abschätzen — Check whether a parked curtain stack intrudes into the opening or handle path.

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": {
      "fenster_frei_soll_cm": "<fenster_frei_soll_cm>",
      "schiene_links_frei_cm": "<schiene_links_frei_cm>",
      "schiene_rechts_frei_cm": "<schiene_rechts_frei_cm>",
      "paket_links_cm": "<paket_links_cm>",
      "paket_rechts_cm": "<paket_rechts_cm>"
    },
    "name": "vorhang_parkbreite_fensterweg"
  }
}

Input Schema

NameRequiredDescriptionDefault
paket_links_cmYesGemessene Breite des gerafften linken Pakets, sonst 0.
paket_rechts_cmYesGemessene Breite des gerafften rechten Pakets, sonst 0.
fenster_frei_soll_cmYesBenötigter freier Bereich in der Ebene des Vorhangs, einschließlich Griffweg.
schiene_links_frei_cmYesNutzbare Parkstrecke links außerhalb dieses Bereichs.
schiene_rechts_frei_cmYesNutzbare Parkstrecke rechts außerhalb dieses Bereichs.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare this as a read-only, closed-world operation. The description adds that the result is an estimate and that it checks for intrusion, but it does not explain calculation assumptions, precision, or what the returned check looks like.

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 compact and front-loaded, with the estimation purpose first and the intrusion-check use case immediately after. There is no filler.

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

Completeness3/5

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

The tool has five required numeric parameters and no output schema. The schema covers the inputs fully and annotations cover safety, but the description does not clarify the return value or precision of the estimate, leaving some contextual detail implicit.

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 required parameters are already well documented in the schema. The description refers to measured fabric stack and operating path, but adds little parameter-level meaning beyond the structured 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 gives a specific verb and resource: estimate the open window width from a measured fabric stack and operating path, and check whether the parked stack intrudes into the opening or handle path. It is clear and concrete, though it does not explicitly distinguish itself from sibling tools.

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?

It states the decision context clearly: use measured fabric-stack widths and the handle/opening clearance to check for intrusion. It does not provide explicit exclusions or name alternative tools, but the intended usage is evident.

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