Skip to main content
Glama

getecoback-climate-weather

klima_abschalttimer_mitternacht

Read-only

Eine Zieluhrzeit nach Mitternacht in die Schritte eines relativen Abschalttimers umrechnen — Set a delay-based overnight switch-off timer at the nearest earlier supported step.

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": {
      "jetzt_min": "<jetzt_min>",
      "aus_uhr_min": "<aus_uhr_min>",
      "schritt_min": "<schritt_min>",
      "maximum_min": "<maximum_min>"
    },
    "name": "klima_abschalttimer_mitternacht"
  }
}

Input Schema

NameRequiredDescriptionDefault
jetzt_minYesAktuelle Uhrzeit in Minuten seit Mitternacht.
aus_uhr_minYesGewünschte Abschaltuhrzeit in Minuten seit Mitternacht. Ein früherer Wert meint den Folgetag.
maximum_minYesGrößte in der Anleitung erlaubte Einstellung in Minuten.
schritt_minYesAbstand der verfügbaren Timer-Einstellungen 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 declare readOnlyHint=true and openWorldHint=false, which matches a pure computation, and the description adds the useful rounding direction (round down to the nearest earlier step) and the fact that the result is a delay-based setting. It does not disclose what the returned value actually is (minutes, step index, or clock time), which matters since 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 compact clauses, with the operation stated before the concrete outcome, and no filler. The German/English duplication is slightly redundant but keeps the intent unambiguous.

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 four-parameter required-argument computation tool with no output schema, the description should say what comes back when no earlier step satisfies the constraints or what unit the result is in. It covers the input-side contract adequately but leaves the output and edge-case behavior unspecified.

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 the four parameters including the cross-midnight interpretation of aus_uhr_min and the cap on maximum_min are already documented. The description only reinforces the rounding relationship between aus_uhr_min and schritt_min, adding little 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?

States a specific verb and resource: converting a target clock time after midnight into steps of a relative switch-off timer, and it names the rounding rule ('nearest earlier supported step'). It does not differentiate against siblings, but no sibling in the list operates on timers, so the risk of confusion is low.

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 overnight/after-midnight scenario is implied by 'nach Mitternacht' and 'overnight switch-off timer', which conveys context for when this applies. There is no explicit when-not guidance, no mention of prerequisites, and no statement of what to do if no earlier supported step exists.

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