Skip to main content
Glama

getecoback-raumklima

mobil_split_gesamtleitung_nutzlaenge_nachweis

Read-only

Trenne veröffentlichte Gesamtlänge und nutzbare Strecke der konkreten Split-Verbindung — Separate the advertised total connection length from its documented usable reach

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": {
      "modell": "<modell>",
      "nutzbar_cm": "<nutzbar_cm>",
      "gemessener_weg_cm": "<gemessener_weg_cm>",
      "nutzlaenge_fuer_aufbau_belegt": "<nutzlaenge_fuer_aufbau_belegt>"
    },
    "name": "mobil_split_gesamtleitung_nutzlaenge_nachweis"
  }
}

Input Schema

NameRequiredDescriptionDefault
modellYesExakt identifizierte Gerätevariante
nutzbar_cmYesFür diesen Aufbau laut Hersteller nutzbare Leitungsstrecke; 0 ohne Bestätigung
gemessener_weg_cmYesVor Ort entlang der vorgesehenen Führung gemessener Weg
nutzlaenge_fuer_aufbau_belegtYesModellanleitung oder Hersteller bestätigt ausdrücklich den nutzbaren Anteil einschließlich Endstücken

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds no behavioral context beyond that: it does not say what the separation result looks like, how the boolean proof flag (nutzlaenge_fuer_aufbau_belegt) affects the outcome, or whether an unconfirmed model/zero usable length produces a rejection or a qualified record.

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?

A single front-loaded clause with a bilingual gloss; there is no filler and the core distinction is stated first. The duplication of the sentence in German and English costs some space but is defensible for a German-domain tool.

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 required-argument 'Nachweis' (evidence) tool with no output schema, the description does not explain what evidence is produced or how the documented-vs-usable separation is resolved when the proof flag is false. The parameters are well documented structurally, but the semantics of the resulting proof are left for the agent to guess.

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% and all four parameters carry their own German descriptions, including enum and range constraints, so the baseline is 3. The description's framing ('veröffentlichte Gesamtlänge' vs 'nutzbare Strecke') loosely maps onto gemessener_weg_cm versus nutzbar_cm, adding a little interpretive value but no format or edge-case detail beyond the schema.

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 action ('Trenne/Separate') and two distinct quantities — the advertised total connection length versus the documented usable reach — so the agent knows this tool produces a separation/evidence record rather than a measurement. It stops short of differentiating itself from plausible siblings such as split_klima_transportweg_masscheck or split_verbindungsleitung_und_abluft_lesen, leaving the boundary implicit.

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?

There is no explicit when-to-use, when-not-to-use, or alternative-tool guidance. The agent must infer from the wording alone that this is the tool for reconciling a datasheet total against the installable usable length, and nothing tells it how this differs from the sibling measurement/read 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