Skip to main content
Glama

getecoback-climate-weather

ventilator_timer_bedienbedarf_nach_abschaltung

Read-only

Plant Neustarts, wenn ein Abschalttimer kürzer als das gewünschte Lüfterfenster ist — Count manual restarts when an off-timer is shorter than a selected fan window.

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": {
      "ziel_min": "<ziel_min>",
      "timer_max_min": "<timer_max_min>",
      "ohne_neustart_geplant": "<ohne_neustart_geplant>"
    },
    "name": "ventilator_timer_bedienbedarf_nach_abschaltung"
  }
}

Input Schema

NameRequiredDescriptionDefault
ziel_minYesGewünschte Lüfterzeit in Minuten.
timer_max_minYesLängste tatsächlich nutzbare Abschaltzeit des Timers in Minuten.
ohne_neustart_geplantYesSoll im gesamten Zeitraum niemand manuell neu starten?

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 safety profile is covered. The description adds the core behavioral rule (restarts are counted only when the off-timer falls short of the target window), but it does not say what the result looks like, how the 'ohne_neustart_geplant' scenario changes the outcome, or how boundary cases are handled — and no output schema exists to fill that 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 sentences with the condition front-loaded and no filler. The German/English duplication is redundant in substance but small, and arguably aids disambiguation of the compound tool name.

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?

For a three-parameter, read-only calculation with no output schema, an agent still lacks a clear statement of the return value and of how the boolean 'ohne_neustart_geplant' modulates the count. The description is adequate but leaves the result shape to inference.

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%, so all three parameters are already documented with units and ranges. The description loosely maps its terms to the parameters (desired fan window, off-timer, manual restarts), but adds no interpretation beyond what the schema fields already say, so the 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 gives a specific computation: count/plan manual restarts when an off-timer is shorter than the desired fan window. The verb-resource pair is concrete and the condition is stated, though the German and English halves use slightly different framings ('Plant Neustarts' vs 'Count manual restarts'), leaving mild doubt about whether output is a plan or a count.

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 description embeds a trigger condition ('when an off-timer is shorter than a selected fan window'), which implies when the tool is relevant. However, it never states when not to use it, nor does it name any sibling tool or alternative approach for the adjacent ventilator-timer scenarios.

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