Skip to main content
Glama

getecoback-raumklima

fensterdichtung_falz_profilabgleich

Read-only

Das Dichtprofil anhand der vorhandenen Nut und seiner angegebenen Spaltbreite prüfen — Match a replacement window gasket to its documented groove and gap range.

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": {
      "spalt_min_mm": "<spalt_min_mm>",
      "spalt_max_mm": "<spalt_max_mm>",
      "profil_min_mm": "<profil_min_mm>",
      "profil_max_mm": "<profil_max_mm>",
      "nut_und_material_bestaetigt": "<nut_und_material_bestaetigt>"
    },
    "name": "fensterdichtung_falz_profilabgleich"
  }
}

Input Schema

NameRequiredDescriptionDefault
spalt_max_mmYesGrößter gemessener Spalt am gleichen Flügel.
spalt_min_mmYesKleinster vor Ort gemessener Spalt am betreffenden Flügel.
profil_max_mmYesOberes geeignetes Spaltmaß laut Unterlagen des Dichtprofils.
profil_min_mmYesUnteres geeignetes Spaltmaß laut Unterlagen des Dichtprofils.
nut_und_material_bestaetigtYesNutform, Anschluss und Material sind für genau dieses Fenster bestätigt?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare this a read-only, closed-world operation, so the safety profile is covered. The description adds that this is a range comparison between field-measured and document-stated values, but it does not disclose the outcome semantics (match/no-match vs. delta reporting) — a real gap given 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.

Conciseness4/5

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

Two short clauses, front-loaded with the German purpose and immediately mirrored in English. The bilingual doubling is redundant for a single-language reader, but it costs little and nothing is buried.

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-required-parameter comparison tool with no output schema, the agent needs to know what a result means and what happens when the ranges do not overlap. The description establishes the inputs but leaves the verdict semantics and the role of the confirmation flag unexplained.

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, including the measured-vs-documented distinction. The description restates the groove and gap-width concepts without adding thresholds, unit handling, or guidance on what a valid range looks like. Baseline 3 applies.

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 verb (prüfen / match) and resource (Dichtprofil an der Nut / replacement window gasket) and identifies the two comparison inputs: the existing groove and the documented gap range. This is clearly distinct in substance from the numeric-only siblings, but no sibling is named for differentiation.

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?

The word 'replacement' (Ersatz) and 'documented range' imply the use case — verifying a candidate gasket before ordering — but the description never states when to use it versus when not, nor that a confirmed groove/material is a precondition for a meaningful answer. Usage is inferable rather than stated.

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