Skip to main content
Glama

getecoback-climate-weather

abluftplatte_lochposition_pruefen

Read-only

Randabstände eines runden Durchlasses für eine vorhandene Fensterplatte prüfen — Check whether a round exhaust cutout leaves the requested edge clearance.

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": {
      "breite_mm": "<breite_mm>",
      "hoehe_mm": "<hoehe_mm>",
      "loch_mm": "<loch_mm>",
      "mitte_x_mm": "<mitte_x_mm>",
      "mitte_y_mm": "<mitte_y_mm>",
      "rand_min_mm": "<rand_min_mm>"
    },
    "name": "abluftplatte_lochposition_pruefen"
  }
}

Input Schema

NameRequiredDescriptionDefault
loch_mmYesVorgesehener Lochdurchmesser gemäß Anschlusszeichnung in mm.
hoehe_mmYesPlattenhöhe in mm.
breite_mmYesPlattenbreite in mm.
mitte_x_mmYesLochmitte vom linken Plattenrand in mm.
mitte_y_mmYesLochmitte vom oberen Plattenrand in mm.
rand_min_mmYesVom gewählten Plattenmaterial und der Befestigung geforderter freier Rand in mm.

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?

The read-only nature is consistent with the annotations, and the description adds that the operation checks whether the requested edge clearance is maintained. It does not explain the result form, such as whether it returns a pass/fail verdict or the computed minimum margin, which matters because there is no output schema.

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 definition is a single front-loaded sentence with the German statement followed by an English equivalent. It contains no filler and immediately identifies the check being performed.

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?

For a six-parameter geometric check, the description identifies the purpose and the key concept of edge clearance, while the schema fully documents the inputs. The main gap is that, with no output schema, the description does not say what the check returns or how a failed clearance is reported.

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 six parameters are already documented with units and bounds. The description reinforces the concepts of round cutout and required edge clearance but adds no parameter-level meaning beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb (prüfen/check) and a precise resource: edge clearances of a round exhaust cutout in an existing window plate. It is specific enough to distinguish this geometric clearance check from broader exhaust-path or placement checks among the siblings.

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 implied by the phrase 'für eine vorhandene Fensterplatte' and the requested edge clearance, so an agent can infer this is for validating a planned round cutout. However, there is no explicit when-to-use guidance, no exclusions, and no named alternative for related checks.

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