Skip to main content
Glama

getecoback-raumklima

ventilator_timer_pause_wiederanlauf_beobachtung

Read-only

Prüft den beobachteten Wiederanlauf mit Timer nach einer regulären Bedienpause — Check timer resumption after a normal control-panel pause.

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": {
      "rest_vor_pause_min": "<rest_vor_pause_min>",
      "pause_min": "<pause_min>",
      "rest_nach_pause_min": "<rest_nach_pause_min>",
      "anzeige_sichtbar": "<anzeige_sichtbar>"
    },
    "name": "ventilator_timer_pause_wiederanlauf_beobachtung"
  }
}

Input Schema

NameRequiredDescriptionDefault
pause_minYesLänge der Pause in Minuten.
anzeige_sichtbarYesWaren beide Timerwerte am Gerät sichtbar?
rest_vor_pause_minYesAngezeigte Restzeit vor der Bedienpause in Minuten.
rest_nach_pause_minYesAngezeigte Restzeit nach dem Wiederanlauf in Minuten.

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 safety behavior is covered and the bar is lower. The description adds the framing that this is an observation-based check rather than a live device query, but it does not state what the check returns (a verdict? a discrepancy report?) or how the four observed values are judged. No contradiction with annotations.

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?

A single compact sentence, front-loaded with the object of the check, followed by an English gloss. The bilingual duplication adds length without adding information, but nothing is wasted or buried.

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 read-only validation tool with four fully documented required parameters, the description covers what is being validated but not what the result looks like or what counts as a pass/fail. With no output schema, some statement of the expected response would have closed the remaining gap.

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% and every parameter carries a clear German description including units and ranges, so the schema does the heavy lifting. The description adds no parameter-level meaning beyond that baseline, merely restating the observation scenario.

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?

Names a specific verb ('Prüft' / 'Check') and a specific resource ('Wiederanlauf mit Timer nach einer regulären Bedienpause'), so the agent knows this validates timer resumption rather than manipulating a timer. It implicitly separates itself from siblings such as ventilator_timer_bedienbedarf_nach_abschaltung by scoping to a 'reguläre Bedienpause', but it does not name any 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 in which the tool applies (after a normal control-panel pause, with observed timer values) is implied by the description, so usage is inferable. There is no explicit when-not guidance, no mention of prerequisites, and no pointer to an alternative tool when the pause was not a regular operation pause.

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