Skip to main content
Glama

getecoback-climate-weather

entfeuchter_raumwechsel_tankrest_zuteilen

Read-only

Grenze die Wassermenge des zweiten Raums ohne Zwischenentleerung ein — Bound the second room’s collected water when a tank was carried over

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": {
      "endstand_l": "<endstand_l>",
      "wechsel_minimum_l": "<wechsel_minimum_l>",
      "wechsel_maximum_l": "<wechsel_maximum_l>",
      "tank_ununterbrochen_belegt": "<tank_ununterbrochen_belegt>"
    },
    "name": "entfeuchter_raumwechsel_tankrest_zuteilen"
  }
}

Input Schema

NameRequiredDescriptionDefault
endstand_lYesGesamter Tankinhalt nach beiden Raumphasen in Litern
wechsel_maximum_lYesGrößter anhand der Übergabenotiz plausibler Tankstand beim Raumwechsel
wechsel_minimum_lYesKleinster anhand der Übergabenotiz plausibler Tankstand beim Raumwechsel
tank_ununterbrochen_belegtYesKein Entleeren, kein Überlaufen und kein Wechsel des Ablaufs dokumentiert

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds the key assumption of no intermediate emptying, but it does not explain how the bound is derived or what result shape to expect.

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?

The description is a single front-loaded sentence with no wasted clauses. The bilingual restatement is redundant but still compact.

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?

With four required numeric/boolean inputs and no output schema, the description should clarify what the computed bound represents and how min/max inputs are used. It gives the scenario but leaves the return semantics implicit.

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 coverage is 100%, so all four parameters are already documented in the input schema. The description connects them conceptually through the carried-over-tank scenario, but adds no parameter-level detail beyond that baseline.

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 operation—bounding the second room’s collected water—and the condition 'when a tank was carried over' / 'ohne Zwischenentleerung'. It is clearly distinct from tank-emptying or logging siblings, though the phrasing is somewhat domain-specific.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a clear usage condition: apply this when the tank was carried over without intermediate emptying. It does not name alternatives or explicit exclusions, but the context is sufficiently clear for selection.

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