Skip to main content
Glama

getecoback-raumklima

lichterkette_timer_einschaltfenster_vergleichen

Read-only

Bei einem bestätigten Tageszyklus prüfen, wie viele gewünschte Einschaltminuten ein gewählter Start tatsächlich trifft. — Intersect a documented daily light timer with the intended clock 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": {
      "timer_start_min": "<timer_start_min>",
      "timer_an_min": "<timer_an_min>",
      "wunsch_start_min": "<wunsch_start_min>",
      "wunsch_dauer_min": "<wunsch_dauer_min>",
      "tageszyklus_bestaetigt": "<tageszyklus_bestaetigt>"
    },
    "name": "lichterkette_timer_einschaltfenster_vergleichen"
  }
}

Input Schema

NameRequiredDescriptionDefault
timer_an_minYesDokumentierte aktive Minuten innerhalb eines genauen 24-Stunden-Zyklus.
timer_start_minYesStart der Einschaltphase als Minuten ab Mitternacht, kleiner als 1440.
wunsch_dauer_minYesLänge des gewünschten Fensters in Minuten, auch über Mitternacht.
wunsch_start_minYesBeginn des gewünschten Fensters als Minuten ab Mitternacht, kleiner als 1440.
tageszyklus_bestaetigtYesGenau dieser Einschaltzyklus wiederholt sich laut Anleitung jeden Tag.

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?

The annotations already declare readOnlyHint=true and openWorldHint=false, so the agent knows this is a safe, closed-world read, and the description is consistent with that. The description adds that the computation is an intersection against a confirmed daily cycle, which is useful behavioral framing. What it never states is what the result looks like (a count of overlapping minutes, a boolean, a shortfall), which is a meaningful omission given there is no output schema.

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, front-loaded with the operating condition and the core computation, with no filler. The English gloss after the dash largely repeats the meaning of the German sentence rather than adding new information, which costs it the top mark.

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 five-parameter, fully required computation tool with no output schema, the description explains the input-side premise (confirmed daily cycle, documented timer versus desired window) adequately. It does not explain the return value or edge-case behavior such as wraparound windows, which are exactly the details an agent needs when no output schema exists.

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 five parameters are already documented in the schema with ranges and meanings, which sets the baseline at 3. The description only loosely maps to the parameters by referring to 'a chosen start' and 'desired switch-on minutes' without adding unit conventions, cross-midnight handling, or semantics beyond what the schema already says.

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 German sentence names a specific operation on a specific object: check how many desired switch-on minutes a chosen start actually hits within a confirmed daily cycle, and the English gloss frames it as intersecting a documented timer with an intended clock window. This is a concrete verb+resource, not a restatement of the name. It stops short of differentiating itself from likely alternatives such as lichterkette_timer_netto, so an agent must infer which comparison variant to pick.

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 phrase 'Bei einem bestätigten Tageszyklus' supplies a precondition tied to the required tageszyklus_bestaetigt flag, which is usable context. However, there is no explicit when-not guidance, no mention of what to do when the cycle is not confirmed, and no pointer to a sibling tool for related calculations. Usage is implied rather than directed.

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