Skip to main content
Glama

getecoback-climate-weather

klima_nachtregime_ziel_und_verbrauch

Read-only

Timer und durchgehenden Betrieb anhand gemessener Energie und Zielzeit vergleichen — Choose the least energy-intensive observed night regime that met your coverage requirement.

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_kwh": "<timer_kwh>",
      "dauerhaft_kwh": "<dauerhaft_kwh>",
      "timer_ziel_min": "<timer_ziel_min>",
      "dauerhaft_ziel_min": "<dauerhaft_ziel_min>",
      "mindest_ziel_min": "<mindest_ziel_min>",
      "vergleichbar": "<vergleichbar>"
    },
    "name": "klima_nachtregime_ziel_und_verbrauch"
  }
}

Input Schema

NameRequiredDescriptionDefault
timer_kwhYesGemessener Verbrauch für die ganze Timernacht. In kWh.
vergleichbarYesGleiche Messdauer, ähnliche Start- und Außenbedingungen und identische Zieldefinition?
dauerhaft_kwhYesGemessener Verbrauch für die Vergleichsnacht mit Dauerprogramm. In kWh.
timer_ziel_minYesMinuten am selbst gesetzten Temperaturziel während der Timernacht. In Minuten.
mindest_ziel_minYesGewünschte Mindestzahl dieser Minuten. In Minuten.
dauerhaft_ziel_minYesEntsprechende Minuten in der Vergleichsnacht. 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 already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds that the tool only reasons over 'observed' measurements, implying no simulation, but it says nothing about what happens when neither regime meets the coverage requirement or what the recommendation contains.

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 sentences, no filler, with the object of comparison stated before the selection goal. Minor deduction for switching from German to English mid-description, which reads slightly disjointed but costs no clarity.

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?

All six required parameters are documented in the schema and the comparison logic is named, but there is no output schema and the description never hints at the return shape — which regime wins, by what margin, or how a coverage failure is reported.

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%, with units, ranges and even a precondition documented on 'vergleichbar', so the schema does the heavy lifting. The description adds only marginal meaning by tying 'Zielzeit' to the coverage requirement (mindest_ziel_min) and stressing that inputs must be measured values.

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 first clause names a concrete verb and two compared resources ('Timer und durchgehenden Betrieb ... vergleichen') scoped by measured energy and target minutes, and the second sentence states the selection objective. The tool's function is unambiguous; only explicit differentiation from near-neighbours like klima_abschalttimer_mitternacht is absent.

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 'Choose the least energy-intensive observed night regime that met your coverage requirement' gives a decision rule, which implies the situation to use it in (you have two measured nights and a minimum target-minutes threshold). It does not state when not to use it, nor does it name any alternative tool for related questions.

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