Skip to main content
Glama

getecoback-climate-weather

stellplatz_tuerschwenk_ueberlagerung

Read-only

Eine geplante Gerätefläche auf Karte gegen die tatsächlich markierte Türbewegung abgleichen — Detect overlap between a device footprint and a measured door-sweep box.

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": {
      "tuer_x_cm": "<tuer_x_cm>",
      "tuer_y_cm": "<tuer_y_cm>",
      "tuer_breite_cm": "<tuer_breite_cm>",
      "tuer_tiefe_cm": "<tuer_tiefe_cm>",
      "geraet_x_cm": "<geraet_x_cm>",
      "geraet_y_cm": "<geraet_y_cm>",
      "geraet_breite_cm": "<geraet_breite_cm>",
      "geraet_tiefe_cm": "<geraet_tiefe_cm>"
    },
    "name": "stellplatz_tuerschwenk_ueberlagerung"
  }
}

Input Schema

NameRequiredDescriptionDefault
tuer_x_cmYesLinke Kante des Hüllrechtecks für den gemessenen Schwenk.
tuer_y_cmYesVordere Kante des Hüllrechtecks; derselbe Maßstab und Nullpunkt für beide Rechtecke.
geraet_x_cmYesLinke Kante der Gerätefläche laut Plan.
geraet_y_cmYesVordere Kante der Gerätefläche laut Plan.
tuer_tiefe_cmYesTiefe des Tür-Hüllrechtecks.
tuer_breite_cmYesBreite des Hüllrechtecks um die gemessene Türbewegung.
geraet_tiefe_cmYesTiefe der vorgesehenen Gerätefläche.
geraet_breite_cmYesBreite der vorgesehenen Gerätefläche.

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 safety is covered. The description adds what is compared but says nothing about computation semantics — whether boundary-touching counts as overlap, whether a tolerance applies, or that both rectangles must share origin and scale (the latter only appears in the schema).

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 front-loaded sentence with the operation first and the two compared objects after; nothing is padding. The bilingual restatement is mildly redundant but serves a German-language tool set usefully.

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?

Eight required numeric parameters are fully documented in the schema, and the read-only annotations cover the safety profile. The missing piece is the return value: with no output schema and no mention in the description, the agent cannot tell whether the result is a boolean, an overlap area, or a per-axis delta.

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%, including the crucial note that both rectangles use the same scale and zero point, so the schema carries parameter meaning fully. The description adds no units, no ordering, and no constraint information beyond the inputs it names implicitly.

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?

Names a specific verb (abgleichen / detect overlap) and two concrete resources — a planned device footprint and a measured door-sweep box — so the operation is unambiguous. It does not, however, distinguish itself from any of the numerous sibling Stellplatz/Abgleich tools, leaving the agent to infer which comparison tool is right.

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?

The description implies the scenario (planned placement vs. actually measured door movement) but gives no explicit when-to-use conditions, no exclusions, and no reference to alternatives. With many similarly named siblings, this absence of routing guidance is a real gap.

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