Skip to main content
Glama

getecoback-raumklima

ventilator_timer_nachtmodus_funktionsgrenze

Read-only

Prüfe, ob Nachtmodus und automatisches Ausschalten laut Anleitung kombinierbar sind — Check whether the fan can combine night mode and automatic shutoff

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": {
      "abschaltung_nach_min": "<abschaltung_nach_min>",
      "timer_max_min": "<timer_max_min>",
      "timer_im_nachtmodus": "<timer_im_nachtmodus>",
      "zeitwert_in_liste": "<zeitwert_in_liste>"
    },
    "name": "ventilator_timer_nachtmodus_funktionsgrenze"
  }
}

Input Schema

NameRequiredDescriptionDefault
timer_max_minYesLängste laut Anleitung wählbare Laufzeit, 0 ohne Timer
zeitwert_in_listeYesGenau dieser Abschaltwert steht in den verfügbaren Timerstufen
timer_im_nachtmodusYesTimer im Nachtmodus ausdrücklich dokumentiert
abschaltung_nach_minYesGewünschte automatische Abschaltung nach Minuten

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/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 and world-scope profile is covered. The description adds that the check is grounded in the manual ('laut Anleitung'), which is meaningful context beyond the annotations. It never states what the verdict looks like (a boolean, a three-state answer matching the 'belegt/ausgeschlossen/offen' enum, or an explanatory reason), which is the main behavioral gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The sentence is front-loaded with the verb and states the constraint immediately, which is good. However, the German and English versions are near-verbatim duplicates, so the same content is delivered twice with no added information — a wasted half of a very short description.

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 four fully documented required parameters, an enum, and no output schema, the schema side is well covered. What is missing is the return semantics of the compatibility check itself and how contradictory inputs (e.g., timer_im_nachtmodus='offen' combined with zeitwert_in_liste=false) are resolved — the agent cannot predict the answer shape for a tool whose entire purpose is producing an answer.

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 one of the four required parameters carries its own German-language description, including the enum values for timer_im_nachtmodus. The description adds no additional parameter meaning (no units, ranges, or interaction between timer_max_min and abschaltung_nach_min), 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 names a specific check ('Prüfe, ob ... kombinierbar sind') against two named features — night mode and automatic shutoff — plus the authority source ('laut Anleitung'). An agent knows precisely what question this tool answers. It does not, however, contrast itself with the many sibling ventilator_timer_* tools, so sibling disambiguation is left to the caller.

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 when-to-use / when-not-to-use guidance, no prerequisites, and no mention of any alternative tool. The phrase 'laut Anleitung' implies this is a documentation-conformance check, but nothing tells an agent when to prefer this over, say, ventilator_wochenbudget_nachtmix or ventilator_timer_bedienbedarf_nach_abschaltung.

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