Skip to main content
Glama

getecoback-raumklima

schlafzimmer_kuehlpause_reserve

Read-only

Aus einer gemessenen Wiedererwärmung abschätzen, wie lange die Kühlpause unter deinem Temperaturziel bleibt — Estimate the remaining off-period before a chosen indoor temperature is reached.

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": {
      "beim_abschalten_c": "<beim_abschalten_c>",
      "spaeter_c": "<spaeter_c>",
      "messdauer_min": "<messdauer_min>",
      "ziel_c": "<ziel_c>",
      "geplante_pause_min": "<geplante_pause_min>"
    },
    "name": "schlafzimmer_kuehlpause_reserve"
  }
}

Input Schema

NameRequiredDescriptionDefault
ziel_cYesPersönliche Komfortmarke. In °C.
spaeter_cYesGemessene Raumtemperatur am Ende der Kühlpause. In °C.
messdauer_minYesDauer der beobachteten Kühlpause in Minuten.
beim_abschalten_cYesGemessene Raumtemperatur am Anfang des Versuchs. In °C.
geplante_pause_minYesGeplante Kühlauszeit unter vergleichbaren Bedingungen. In Minuten.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already establish this as a read-only, closed-world computation, so the safety profile needs no restating. The description adds the useful qualifier that the result rests on a measured rewarming, i.e. it is an inference, not a measurement. It does not disclose the underlying model (apparently linear rewarming extrapolation) or what happens when the observed data is inconsistent or when the measured rise is negative, which is where misuses would occur.

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?

A single front-loaded sentence with the purpose first, which is well structured. The German/English doubling is mild redundancy, though defensible for a German-language toolset; each version is otherwise free of filler.

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?

With five required numeric parameters and no output schema, the description should clarify what comes back (a remaining duration in minutes? a margin against the planned pause?) and how the scheduled pause enters the comparison. It conveys the conceptual answer but leaves the result shape and the role of geplante_pause_min unaddressed.

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 every parameter already carries units, bounds, and meaning; baseline is 3. The description reinforces two of them semantically (the comfort target via "dein Temperaturziel", the measured curve via "gemessene Wiedererwärmung") but adds no format or relationship detail. Notably it never mentions geplante_pause_min, so the role of that required parameter in the calculation stays unexplained.

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 pairs a specific verb ("abschätzen"/"estimate") with a concrete computed quantity: the remaining off-period before a chosen indoor temperature is reached, derived from a measured rewarming. An agent can tell this is an extrapolation/calculation tool rather than a measurement-logging tool. It stops short of naming a distinguishing sibling, but the resource and operation are unambiguous.

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, no prerequisites, and no pointer to alternatives such as the other Schlafzimmer measurement siblings. The only hint is implicit: the tool presumes an already-recorded rewarming observation. An agent must infer the invocation context entirely from the parameter names.

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