Skip to main content
Glama

getecoback-raumklima

entfeuchter_zwei_raeume_tank_zwischenstopp

Read-only

Zwei beobachtete Entfeuchterläufe gegen den verfügbaren Tank und einen Entleerungstermin prüfen — Check reservoir headroom across two measured room sessions.

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": {
      "nutzbare_l": "<nutzbare_l>",
      "anfang_l": "<anfang_l>",
      "a_erwartet_l": "<a_erwartet_l>",
      "b_erwartet_l": "<b_erwartet_l>",
      "entleerung_dazwischen": "<entleerung_dazwischen>"
    },
    "name": "entfeuchter_zwei_raeume_tank_zwischenstopp"
  }
}

Input Schema

NameRequiredDescriptionDefault
anfang_lYesBereits im Tank befindliche Wassermenge in Litern.
nutzbare_lYesBekannte nutzbare Tankmenge dieses Geräts in Litern.
a_erwartet_lYesIn Raum A bei vergleichbarem Versuch gesammelte Liter.
b_erwartet_lYesIn Raum B bei vergleichbarem Versuch gesammelte Liter.
entleerung_dazwischenYesIst die vollständige Entleerung zwischen den beiden Läufen bestätigt?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior2/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 no behavioral context beyond that: it does not say what the check yields (a boolean verdict, per-run overflow amounts, the latest feasible drain point) or whether the emptying flag relaxes the constraint. For a pure computation tool with no output schema, that is a meaningful gap.

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?

Two short clauses that front-load the resource and the scenario; nothing extraneous. The German/English duplication is deliberate rather than padding, though it does mean the same content is stated twice.

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 inputs are fully specified and the scenario is easy to grasp, but with no output schema the description should state what an agent receives back and how the two-run comparison is resolved. That return-side information is the main missing piece for a five-required-parameter check tool.

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 five parameters (usable tank volume, initial fill, expected liters for rooms A and B, confirmed emptying between runs) are already documented in the schema. The description only frames them collectively as two runs plus a drain appointment and adds no units, ordering, or edge-case meaning beyond that.

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 a specific verb (prüfen/check) and a precise resource: reservoir headroom across two observed dehumidifier runs with a drain appointment in between. That is clearly distinguishable from siblings about leak intervals or tank-rest allocation, though it never names a sibling explicitly.

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

Usage Guidelines3/5

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

The scenario implies when to use it (two measured room sessions with a possible emptying between them), but there is no explicit when-not condition and no pointer to alternatives such as entfeuchter_tank_leerintervall or entfeuchter_tank_zwischenablage_abgleichen. Usage must be inferred from the described situation.

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