Skip to main content
Glama

getecoback-raumklima

entfeuchter_tank_zwischenablage_abgleichen

Read-only

Eine vorgesehene Zwischenablage für den entnommenen Tank mit den gemessenen Tankmaßen abgleichen — Check usable shelf dimensions for a removed dehumidifier tank.

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": {
      "tank_breite_cm": "<tank_breite_cm>",
      "tank_tiefe_cm": "<tank_tiefe_cm>",
      "ablage_breite_cm": "<ablage_breite_cm>",
      "ablage_tiefe_cm": "<ablage_tiefe_cm>"
    },
    "name": "entfeuchter_tank_zwischenablage_abgleichen"
  }
}

Input Schema

NameRequiredDescriptionDefault
tank_tiefe_cmYesTatsächliche äußere Tiefe des Tanks.
tank_breite_cmYesTatsächliche äußere Breite des abnehmbaren Tanks in seiner vorgesehenen Position.
ablage_tiefe_cmYesFrei nutzbare Tiefe der ebenen Ablage in cm.
ablage_breite_cmYesFrei nutzbare Breite der ebenen Ablage in cm.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/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 and locality are covered. The description adds the comparison semantics (tank dimensions against usable shelf area) but says nothing about the result form — fit/no-fit, clearance margin, tolerance — which is the main behavioral unknown for a pure computation tool.

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 short sentence, front-loaded with the object being compared. The bilingual duplication is mild waste and the English half partly restates rather than sharpens the German half, but nothing is bloated.

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 inputs are fully documented in the schema and there is no output schema, so the description need not explain return values. Still, for a tool whose entire purpose is a comparison, omitting whether the result is a boolean fit check, a margin, or a dimension report leaves a real gap.

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%: every one of the four required parameters has a precise German description including units and whether it is the tank or the shelf measurement. The description adds no additional meaning beyond that, so the baseline 3 applies.

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 a verb ("abgleichen") and the two resources being compared (tank outer dimensions vs. usable shelf area), and the English gloss clarifies the intent. However, the term "Zwischenablage" is genuinely ambiguous in German (commonly 'clipboard'), and the sentence never states the comparison outcome or how this differs from the many other '*_abgleichen' siblings.

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 phrase "für den entnommenen Tank" — i.e. after removing the tank and measuring it. There is no explicit when-to-use condition, no exclusion, and no pointer to related siblings such as entfeuchter_leerer_tank_check or entfeuchter_ablaufcheck, which an agent would need to disambiguate.

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