Skip to main content
Glama

getecoback-climate-weather

abluftanschluss_kupplung_abgleichen

Read-only

Die Steckverbindung eines Monoblock-Abluftadapters nach Anschlussart und maßgeblichem Durchmesser prüfen — Compare the actual mating diameters and connector types of an exhaust cuff.

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": {
      "stutzen_aussen_mm": "<stutzen_aussen_mm>",
      "muffe_innen_mm": "<muffe_innen_mm>",
      "spiel_min_mm": "<spiel_min_mm>",
      "spiel_max_mm": "<spiel_max_mm>",
      "gleiche_anschlussart": "<gleiche_anschlussart>"
    },
    "name": "abluftanschluss_kupplung_abgleichen"
  }
}

Input Schema

NameRequiredDescriptionDefault
spiel_max_mmYesDokumentiertes oberes diametrales Spiel für die Steckverbindung.
spiel_min_mmYesDokumentiertes unteres diametrales Spiel für die Steckverbindung.
muffe_innen_mmYesInnendurchmesser der vorgesehenen Gegenmuffe laut Maßblatt.
stutzen_aussen_mmYesAußendurchmesser des vorgesehenen Steckstutzens laut Maßblatt.
gleiche_anschlussartYesAnschlussart, Verriegelung und Freigabe für das konkrete Gerät wurden als passend dokumentiert?

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?

The annotations already establish the safety profile (readOnlyHint=true) and closed-world behavior (openWorldHint=false), so the description carries a light burden. It adds that the check is a diameter and connector-type comparison, which is useful context. It does not disclose the decision rule, the tolerance-band behavior, or the result shape, 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.

Conciseness4/5

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

Two short sentences, both front-loaded, with no filler. The German and English halves restate the same content, so the second sentence is largely redundant, but nothing is wasted or 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?

The tool is a five-parameter comparison with no output schema, so the description must carry the burden of explaining what the comparison yields. It names the inputs being compared but not the verdict, the decision criteria, or the units' role. An agent knows what to feed in, but not what it will get back or how to read it.

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 every one of the five required parameters is already documented in German, including the male outside diameter, the female inside diameter, the min/max diametral play, and the 'gleiche Anschlussart' flag. The description adds only the framing of 'maßgeblicher Durchmesser' and 'Anschlussart'. It does not explain how the two play parameters are applied, for example whether they form the acceptance band.

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 gives a specific verb (prüfen/compare) and a specific resource: the mating diameters and connector type (Anschlussart) of a Monoblock exhaust adapter's plug connection. That is far more concrete than a restated name. However, it never says what the check produces (a pass/fail verdict versus a measured deviation) and it does not distinguish this tool from the many sibling *_abgleichen checks.

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?

Usage is only implied by the domain vocabulary 'Steckverbindung' and 'maßgeblicher Durchmesser'. There is no explicit statement of when to use this tool, no prerequisite (for example, that the mating-part dimensions must first come from a datasheet), and no exclusion or alternative named among the numerous sibling *_abgleichen tools.

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