Skip to main content
Glama

getecoback-climate-weather

stapelsaeule_oberes_bedienfeld_und_tankgriff

Read-only

Ans Bedienfeld reichen und einen Kondenswasserbehälter handhaben als getrennte Anforderungen prüfen — Compare projected access for two different upper-unit tasks.

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": {
      "messbasis_bestaetigt": "<messbasis_bestaetigt>",
      "unterkante_trockner_mm": "<unterkante_trockner_mm>",
      "bedienfeld_ab_unten_mm": "<bedienfeld_ab_unten_mm>",
      "tankgriff_ab_unten_mm": "<tankgriff_ab_unten_mm>",
      "eigene_bediengrenze_mm": "<eigene_bediengrenze_mm>",
      "eigene_tankgrenze_mm": "<eigene_tankgrenze_mm>"
    },
    "name": "stapelsaeule_oberes_bedienfeld_und_tankgriff"
  }
}

Input Schema

NameRequiredDescriptionDefault
eigene_tankgrenze_mmYesSelbst beobachtete Reichhöhe für den vorgesehenen Umgang mit dem Behälter.
messbasis_bestaetigtYesSind Unterkante des Trockners und Griffhöhen im gleichen geplanten Fußbodenbezug dokumentiert?
tankgriff_ab_unten_mmYesTankgriff oberhalb dieser Unterkante.
bedienfeld_ab_unten_mmYesBedienpunkt oberhalb dieser Unterkante.
eigene_bediengrenze_mmYesSelbst beobachtete bequeme Reichhöhe für kurze Betätigung.
unterkante_trockner_mmYesAbgesicherte geometrische Höhe der Trocknerunterkante.

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 already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds that this is a projected/comparative assessment rather than a measurement recording, which is useful. However, it does not disclose what happens when messbasis_bestaetigt is false (error, warning, or reduced confidence) — a meaningful behavioral gap for a purely evaluative tool with 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?

A single front-loaded sentence with the two tasks named first and the comparison framing second; no filler. The German compound phrasing is dense but nothing is redundant.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Placeholder

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 six parameters is already documented with units and meaning in the schema. The description adds no parameter-specific semantics beyond the general framing of two separate access tasks, 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 two concrete resources — reaching the control panel (Bedienfeld) and handling the condensate tank handle (Tankgriff) — and frames the operation as a comparison of projected access. That is a specific verb-plus-resource statement an agent can act on, though it never says what form the comparison result takes.

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 sentence 'als getrennte Anforderungen prüfen' implies the situation (two upper-unit access requirements assessed separately), but there is no explicit when-to-use, no when-not, and no routing to or away from siblings such as stapelsaeule_tank_vollentnahme_und_arbeitsfreiraum or stapelsaeule_auszug_und_tuer_gemeinsamer_betriebsraum.

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