Skip to main content
Glama

getecoback-climate-weather

fensterrahmen_diagonalen_vor_zuschnitt

Read-only

Vor rechteckigem Zuschnitt die beiden Diagonalen der Einbauebene auf bedeutsame Abweichung prüfen — Compare measured frame diagonals with the rectangle implied by width and height.

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_cm": "<breite_cm>",
      "hoehe_cm": "<hoehe_cm>",
      "diagonal_a_cm": "<diagonal_a_cm>",
      "diagonal_b_cm": "<diagonal_b_cm>",
      "messtoleranz_cm": "<messtoleranz_cm>"
    },
    "name": "fensterrahmen_diagonalen_vor_zuschnitt"
  }
}

Input Schema

NameRequiredDescriptionDefault
hoehe_cmYesHöhe der vorgesehenen Einbauebene.
breite_cmYesBreite der vorgesehenen Einbauebene.
diagonal_a_cmYesErste gemessene Eckdiagonale in derselben Ebene.
diagonal_b_cmYesZweite gemessene Eckdiagonale in derselben Ebene.
messtoleranz_cmYesEigene Toleranz für das Aufmaß.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/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 operation. The description adds that the tool compares measured diagonals against the rectangle implied by width and height, but it does not explain how 'bedeutsame Abweichung' is determined, how messtoleranz_cm is applied, or what kind of result is returned.

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?

The definition is short and front-loads the usage context before the comparison logic. The German sentence and English gloss are somewhat redundant, but the duplication aids clarity and does not create unnecessary bulk.

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 five-parameter read-only check tool, the description explains the core comparison but leaves the output semantics and tolerance behavior implicit. With no output schema, an agent would still lack information about what the tool returns when a deviation is or is not significant.

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 parameters are already documented. The description adds the conceptual relationship between the measured diagonals and the width/height rectangle, but it does not clarify the role of messtoleranz_cm beyond implying a tolerance check.

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 states a specific action: checking the two diagonals of the installation plane for significant deviation before rectangular cutting. It also clarifies that measured diagonals are compared with the rectangle implied by width and height. It does not explicitly distinguish itself from any sibling tool, which keeps it from a 5.

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 'Vor rechteckigem Zuschnitt' gives a clear usage context: this check should happen before cutting. It does not name alternatives or exclusions, but the timing guidance is explicit enough for an agent to know when to invoke it.

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