Skip to main content
Glama

getecoback-climate-weather

ventilator_stufenwahl_tastendruecke

Read-only

Bei nachweislich zyklischer Lüftersteuerung die Zahl der Tastendrücke bis zur Zielstufe ermitteln — Count presses needed on a documented cyclic fan control.

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": {
      "stufen": "<stufen>",
      "aktuell": "<aktuell>",
      "ziel": "<ziel>",
      "zyklus": "<zyklus>"
    },
    "name": "ventilator_stufenwahl_tastendruecke"
  }
}

Input Schema

NameRequiredDescriptionDefault
zielYesGewünschte Position, in derselben Reihenfolge.
stufenYesZahl der Positionen im belegten Umlauf ohne separate Aus-Taste.
zyklusYesEin Druck schaltet laut Modellanleitung oder direktem Test genau eine Position weiter und springt danach zu 1?
aktuellYesAktuelle Position, von 1 bis zur Zahl der Positionen.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The annotations cover the operational safety profile (readOnlyHint=true, openWorldHint=false). The description adds context regarding the system's behavior (it must be cyclic) rather than adding novel behavioral traits not implied by the schema or annotations.

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

Conciseness5/5

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

The definition is extremely concise and efficient. It presents a complex, niche logic in a single, high-impact sentence with no filler or superfluous language.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity of the calculation, the description is complete because it defines the exact scenario and the required logical output. The high schema coverage means the description correctly frames the tool's necessity without needing to explain input types or return values.

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?

Since the schema description coverage is 100%, the schema already defines all parameter meanings precisely. The description frames the collective purpose of the parameters (finding the press count), which is helpful but adds no semantic value beyond the structural data provided.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The purpose is highly specific, identifying the exact action (count keystrokes) and the required condition (cyclic fan control). This specialized logic clearly distinguishes it from general fan operation or remote command tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly states when the tool should be used: 'Bei nachweislich zyklischer Lüftersteuerung' (when cyclic fan control is documented). This strong dependency acts as a clear usage gate for the agent.

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