Skip to main content
Glama

getecoback-raumklima

gebraucht_klimageraet_abluftstrecke_uebergabezustand

Read-only

Den sichtbaren Zustand der mitgegebenen, getrennt betrachteten Abluftteile dokumentieren — Separate accessory condition at each end from the state of the flexible span.

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": {
      "nur_aussen_einsehbar": "<nur_aussen_einsehbar>",
      "erstes_ende": "<erstes_ende>",
      "zweites_ende": "<zweites_ende>",
      "schlauchstrecke": "<schlauchstrecke>"
    },
    "name": "gebraucht_klimageraet_abluftstrecke_uebergabezustand"
  }
}

Input Schema

NameRequiredDescriptionDefault
erstes_endeYesBeobachtung am ersten lösbaren Anschlussstück.
zweites_endeYesBeobachtung am anderen lösbaren Anschlussstück.
schlauchstreckeYesBeobachtung an der einsehbaren Außenhülle.
nur_aussen_einsehbarYesSind die drei Bereiche ohne Öffnen des Geräts laut Anleitung sichtbar und eindeutig dem Satz zugeordnet?

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 declare readOnlyHint=true and openWorldHint=false, so the safety profile is already covered. The description adds a useful constraint beyond that — only *visible* condition counts — but leaves open what 'dokumentieren' actually produces (a persisted record versus a returned observation) and whether 'unbekannt' values abort or pass, which is the main behavioral ambiguity an agent faces here.

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?

One compact sentence with the purpose front-loaded and the partitioning rule appended, with no filler. The bilingual German/English construction is slightly awkward and the em-dash split reads as an afterthought, but nothing is wasteful.

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?

All four required parameters are schema-documented and there is no output schema to explain, so the remaining gap is modest. Still, for a tool whose name implies a handover record, the description does not state what the recorded artefact is or what happens when visibility fails, leaving an agent to guess at edge-case behavior.

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% with enum values documented inline, so the schema carries the parameter burden and the baseline is 3. The description reinforces the three-zone decomposition and the visibility restriction, but adds no interpretation of the enum levels or of how nur_aussen_einsehbar gates the other three fields.

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 ('dokumentieren') and a well-scoped resource: the visible condition of the supplied exhaust parts, split into two ends and the flexible span. An agent can tell this is a structured observation-recording tool rather than a diagnostic one, although the resource granularity (three zones) is only fully conveyed by pairing the German sentence with its English gloss.

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 clause 'Separate accessory condition at each end from the state of the flexible span' gives recording guidance on how to partition observations, which implies the intended usage. However, there is no explicit when-to-use, no when-not-to-use, and no routing to or from the many related siblings (e.g. gebraucht_dichtung_zugangsabschnitte_sichtbefund, abluftanschluss_kupplung_abgleichen), so an agent must infer the boundary itself.

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