Skip to main content
Glama

getecoback-climate-weather

entfeuchter_mindestpause_zeitplan

Read-only

Eine Wiederanlaufpause des Entfeuchters gegen das nächste begrenzte Betriebsfenster rechnen — Schedule the next dehumidification interval using the exact documented restart delay.

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": {
      "zuletzt_aus_min": "<zuletzt_aus_min>",
      "fenster_ab": "<fenster_ab>",
      "fenster_bis": "<fenster_bis>",
      "wiederanlaufpause_min": "<wiederanlaufpause_min>",
      "pause_bekannt": "<pause_bekannt>"
    },
    "name": "entfeuchter_mindestpause_zeitplan"
  }
}

Input Schema

NameRequiredDescriptionDefault
fenster_abYesBeginn des Verfügbarkeitsfensters. Minuten seit Beginn des Planungstages, bei Bedarf über Mitternacht hinaus.
fenster_bisYesEnde des Verfügbarkeitsfensters. Minuten seit Beginn des Planungstages, bei Bedarf über Mitternacht hinaus.
pause_bekanntYesIst die Restart-Regel für dieses Gerät und diese Betriebsart dokumentiert?
zuletzt_aus_minYesZeitpunkt des letzten Stopps. Minuten seit Beginn des Planungstages, bei Bedarf über Mitternacht hinaus.
wiederanlaufpause_minYesNachgewiesene Mindestpause für den konkreten Betriebszustand. In Minuten.

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 safety is covered and the bar is lower. The description usefully signals that this is a pure computation requiring the exact documented delay rather than an estimate. It does not disclose what the tool returns, what happens when pause_bekannt is false, or any constraints on an empty operating window, which are the meaningful behavioral gaps here.

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 sentences, front-loaded with the German statement of the operation. The bilingual restatement is mildly redundant but each half adds a nuance (the window constraint, the 'exact documented' requirement), so little is pure waste.

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 five required numeric/boolean inputs and no output schema, the definition leaves the return value entirely unspecified, so an agent cannot anticipate the shape of the computed schedule. Input semantics are fully covered by the schema and the description correctly frames this as a deterministic calculation, but the result-side ambiguity keeps it at minimum-viable completeness.

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%, with all five parameters documented including units, ranges and the planning-day minute convention, so the schema carries the semantics. The description adds only the qualifier 'exact documented' tying pause_bekannt to wiederanlaufpause_min, with no further interpretation of how fenster_ab/fenster_bis/zuletzt_aus_min interact. Baseline 3 applies.

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 operation: computing a restart pause against the next limited operating window (schedule the next dehumidification interval from the documented restart delay). The verb 'rechnen/schedule' plus the resource 'Wiederanlaufpause/Betriebsfenster' is concrete enough to act on. It stops short of distinguishing itself from the other *_zeitplan siblings, so an agent cannot tell from the text alone why this scheduler differs from geraetelauf_aufsichtswechsel_zeitplan or thermostat_uebergang_zeitplan_umgehung.

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?

There is no explicit when-to-use or when-not-to-use guidance and no named alternative. The only implied condition is that the restart delay must be documented ('exact documented restart delay', mirrored by the pause_bekannt parameter), but the description never says what to do if it is not, nor when a sibling scheduler would be the better choice.

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