Skip to main content
Glama

getecoback-raumklima

entfeuchter_tankweg_tragstrecke

Read-only

Die in einem eigenen Zeitraum mit dem gefüllten Tank zurückgelegten Meter für zwei geplante Standorte vergleichen — Compare repeated carrying distance to the emptying point for two dehumidifier locations.

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": {
      "weg_a_m": "<weg_a_m>",
      "weg_b_m": "<weg_b_m>",
      "leerungen_a": "<leerungen_a>",
      "leerungen_b": "<leerungen_b>",
      "vergleichbare_raumziele": "<vergleichbare_raumziele>"
    },
    "name": "entfeuchter_tankweg_tragstrecke"
  }
}

Input Schema

NameRequiredDescriptionDefault
weg_a_mYesAm realen Weg gemessene einfache Tragstrecke von Standort A bis zur Entleerung.
weg_b_mYesAm realen Weg gemessene einfache Tragstrecke von Standort B.
leerungen_aYesBeobachtete Zahl der Tankentleerungen an A im Vergleichszeitraum.
leerungen_bYesBeobachtete Zahl der Tankentleerungen an B in genauso vielen Tagen.
vergleichbare_raumzieleYesVergleichbare Zielbedingungen und vom Handbuch gedeckte Aufstellung an beiden Orten?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/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 the safety profile is covered. The description adds a little beyond that by framing the metric as repeated carrying distance over an own time period (implying distance x emptying count) and requiring planned sites, but it says nothing about the computation result, units, or what happens when conditions are not comparable.

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 per language with no wasted clauses; the bilingual duplication is conventional and costs little, though the English half is a paraphrase rather than a complement.

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?

There is no output schema, so the description should convey what the comparison yields (total meters, ratio, verdict), and it does not. For a five-parameter pure-computation tool with complete parameter docs this is adequate but leaves a real gap about the returned result.

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 each of the five parameters carries a precise German explanation, so the schema does the heavy lifting. The description only implies the interaction between Weg and Leerungen via 'repeated carrying distance' and adds no syntax, unit, or edge-case meaning 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 states a specific verb (vergleichen/compare) and a specific resource (the carrying distance to the emptying point for two dehumidifier sites over a defined period), so an agent can tell what the tool computes. It does not, however, name or distinguish itself from the many other tank/interval siblings such as entfeuchter_tank_leerintervall.

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: the two-site, defined-period framing hints at a comparison scenario, but there is no explicit when-to-use, no when-not-to-use, and no reference to an alternative tool. An agent facing several tank-related siblings gets no routing help.

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