Skip to main content
Glama

getecoback-climate-weather

abluft_anschluss_nennweite_messkante

Read-only

Prüfe, ob Soll- und Angebotsdurchmesser an derselben Anschlusskante stehen — Check that exhaust fitting diameters refer to the same interface

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": {
      "soll_mm": "<soll_mm>",
      "angebot_mm": "<angebot_mm>",
      "soll_kante": "<soll_kante>",
      "angebot_kante": "<angebot_kante>",
      "freigabe": "<freigabe>"
    },
    "name": "abluft_anschluss_nennweite_messkante"
  }
}

Input Schema

NameRequiredDescriptionDefault
soll_mmYesDurchmesser am Originalanschluss laut Modellunterlage
freigabeYesFreigabe des Zubehörs für die genaue Gerätevariante
angebot_mmYesDurchmesser laut Zubehörzeichnung
soll_kanteYesBezugsfläche beim Original
angebot_kanteYesBezugsfläche beim Zubehör

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior2/5

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

Annotations only declare readOnlyHint and openWorldHint=false, which cover safety but not outcome. The description never says what a check produces (pass/fail flag, mismatch message) and, with no output schema, the return value is entirely undocumented. It also does not mention what happens when the edges differ or whether 'freigabe' gates the verdict.

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, front-loaded sentences with the core check stated first. The bilingual restatement is mild duplication but adds little waste and helps disambiguation.

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

Completeness2/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 and only minimal annotations, the definition leaves the agent guessing about the result format and failure semantics. It should state what is returned and how 'freigabe' interacts with the diameter/edge comparison.

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, including the drei enums, are already self-documenting. The description adds no syntax, unit, or edge-case meaning beyond what the schema states, so the 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üfe/Check') and a specific resource ('Soll- und Angebotsdurchmesser an derselben Anschlusskante'), so the agent knows this is a consistency check between target and quoted diameters. It does not distinguish itself from the lookalike sibling 'abluftanschluss_kupplung_abgleichen', which prevents 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The check scenario is implied by the wording, but there is no explicit when-to-use, when-not-to-use, or pointer to a sibling such as the coupling-alignment tool. The agent must infer that this runs as a verification step before accepting an accessory offer.

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