Skip to main content
Glama

getecoback-raumklima

stapelsaeule_tank_vollentnahme_und_arbeitsfreiraum

Read-only

Den langen Auszug eines Kondenswasserbehälters von bloßer Erreichbarkeit seines Griffs unterscheiden — Check the full removal envelope as well as separate carrying room.

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": {
      "tankweg_geprueft": "<tankweg_geprueft>",
      "freie_tiefe_mm": "<freie_tiefe_mm>",
      "voll_entnahme_mm": "<voll_entnahme_mm>",
      "eigene_arbeitsreserve_mm": "<eigene_arbeitsreserve_mm>",
      "trageweg_verlegt": "<trageweg_verlegt>"
    },
    "name": "stapelsaeule_tank_vollentnahme_und_arbeitsfreiraum"
  }
}

Input Schema

NameRequiredDescriptionDefault
freie_tiefe_mmYesFreie Tiefe vor der Gerätefront entlang der Entnahme.
tankweg_geprueftYesIst der vorgesehene Entnahmeweg dieses Behälters aus der passenden Anleitung oder einer tatsächlichen unbelasteten Beobachtung bekannt?
trageweg_verlegtYesIst nach der Entnahme ein davon unabhängiger, tatsächlich verfügbarer Trageweg bestätigt?
voll_entnahme_mmYesÄußerster Punkt des vollständigen Entnahmewegs ab Front.
eigene_arbeitsreserve_mmYesZusätzlich selbst benötigter gleichzeitig freier Bereich entlang derselben Tiefenlinie.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds the useful conceptual point that full removal distance and independent carrying room are two separate things to confirm, which is beyond the annotations. However it does not describe what conclude/verdict a check produces, whether it blocks or merely reports, or how the inputs combine.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The definition is very short (two clauses) and front-loaded, so there is little waste. But the compactness comes partly from figurative phrasing that sacrifices precision, so it is under-specified rather than genuinely efficient.

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?

This is a five-parameter, all-required check tool with no output schema, so the description carries real burden to explain how the checks resolve. It instead stays at a conceptual level and never addresses the boolean-flag logic (tankweg_geprueft, trageweg_verlegt) or what a passing/failing assessment requires. For this complexity the description is inadequate.

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 in the schema. The description's reference to the removal envelope and separate carrying room loosely maps onto voll_entnahme_mm and trageweg_verlegt, but adds no syntax, units, or relationships beyond the schema. Baseline 3 is appropriate when the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the two things being checked - the full removal envelope and the separate carrying room - for the condensate container. But it uses figurative framing ("den langen Auszug ... unterscheiden") rather than stating a concrete verb like verify/compute, so the actual operation is only implied. A reader can grasp the subject matter but not precisely what action is performed.

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?

The description contrasts the concept with "mere reachability of the handle," which is conceptual framing, not a when-to-use instruction. It never says when to choose this tool versus the many stapelsaeule siblings that also deal with extraction and clearance (e.g. the auszug/tür or oberes_bedienfeld tools). No prerequisites or exclusions are given.

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