Skip to main content
Glama

getecoback-raumklima

keller_entfeuchter_saisonstunden_abdeckung

Read-only

Erfasste Kellerstunden nach einem bestätigten unteren Einsatztemperaturwert einordnen — Estimate how much of a sampled cold-season dehumidification window falls within the documented temperature range.

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": {
      "anleitung_min_c": "<anleitung_min_c>",
      "anleitung_max_c": "<anleitung_max_c>",
      "kuehl_c": "<kuehl_c>",
      "kuelldauer_h": "<kuelldauer_h>",
      "mild_c": "<mild_c>",
      "milddauer_h": "<milddauer_h>",
      "grenzen_bekannt": "<grenzen_bekannt>"
    },
    "name": "keller_entfeuchter_saisonstunden_abdeckung"
  }
}

Input Schema

NameRequiredDescriptionDefault
mild_cYesTemperatur im milderen protokollierten Zeitblock. In °C.
kuehl_cYesTemperatur im kühlen protokollierten Zeitblock. In °C.
milddauer_hYesDauer des milden Zeitblocks in Stunden.
kuelldauer_hYesDauer des kühlen Zeitblocks in Stunden.
anleitung_max_cYesBestätigte obere Einsatztemperatur. In °C.
anleitung_min_cYesBestätigte untere Einsatztemperatur des konkreten Geräts. In °C.
grenzen_bekanntYesBeide Einsatzgrenzen wurden für die Gerätevariante nachgewiesen?

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 the agent knows this is a safe, closed-world computation. The description adds that the estimate is tied to a sampled cold-season window and a documented range, but it does not explain the basis of the calculation or how partial coverage is handled.

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 compact, front-loaded sentences with no filler. The bilingual German/English pairing is somewhat redundant but provides cross-language clarity rather than padding.

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 7 required parameters, no output schema, and only read-only annotations, the description should say what the estimate returns (a ratio, percentage, or hours). It hints at 'how much ... falls within' but never specifies the result format, leaving a material gap for a computation 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?

All 7 parameters are fully documented in the schema (100% coverage), so the schema carries the heavy lifting. The description only loosely echoes the two limit parameters ('bestätigten unteren Einsatztemperaturwert,' 'documented temperature range') and adds no syntax or semantics 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 names a concrete operation (classify recorded cellar hours / estimate how much of a cold-season dehumidification window falls within the documented range) and the resource (temperature-bounded window). It is identifiable on its own, though the German and English halves phrase the operation slightly differently, and it does not distinguish itself from any of the many sibling entfeuchter_* tools.

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?

Usage is implied by the phrasing 'nach einem bestätigten unteren Einsatztemperaturwert' and 'documented temperature range,' which signal the prerequisite evidence. However, there is no explicit when-to-use, no when-not, and no named alternative among the many sibling tools.

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