Skip to main content
Glama

getecoback-raumklima

klimageraet_ein_aus_timer_kombinationsbeleg

Read-only

Ein geplantes Klimafenster gegen dokumentierten Starttimer, Stopptimer und deren gleichzeitige Nutzbarkeit prüfen. — Verify that both ends of an AC window can be automated together.

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": {
      "einschalten": "<einschalten>",
      "ausschalten": "<ausschalten>",
      "kombiniert": "<kombiniert>"
    },
    "name": "klimageraet_ein_aus_timer_kombinationsbeleg"
  }
}

Input Schema

NameRequiredDescriptionDefault
kombiniertYesStand der Anleitung zur gleichzeitigen Programmierung beider Ereignisse im selben Modus.
ausschaltenYesStand der Anleitung für einen Ausschalt-Timer.
einschaltenYesStand der Anleitung für einen Einschalt-Timer.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior2/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 no behavior beyond that: it does not say how the three status values are combined into a verdict, what the response looks like (no output schema exists), or how 'offen' differs behaviorally from 'fehlt'.

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, purpose front-loaded, no filler. The English sentence largely restates the German one, which is mildly redundant but genuinely useful for non-German readers rather than padding.

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 simple three-enum read-only check, the description explains the inputs' meaning adequately. It is incomplete on the outcome side: with no output schema, the agent has no idea what the tool returns or how conflicting status combinations are resolved.

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 each of the three enum parameters is documented in the schema itself, so the baseline is 3. The description's mention of Starttimer, Stopptimer, and gleichzeitige Nutzbarkeit loosely maps to einschalten, ausschalten, and kombiniert, but adds no format or interpretation detail beyond the schema.

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 action (prüfen/verify) and a specific subject: whether a planned AC window can be automated at both ends, based on documented start timer, stop timer, and their simultaneous programmability. This is concrete enough to distinguish it from a generic device-status tool, though it never contrasts itself with near-siblings such as klimageraet_timer_moduswechsel_uebergang.

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 alternative tool is named. The agent must infer from the verb 'prüfen' that this is a pre-check before scheduling an AC window; nothing states prerequisites or what to do with a 'fehlt' or 'offen' result.

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