Skip to main content
Glama

getecoback-climate-weather

heizpause_durchlaufen_wiederaufheizen

Read-only

Für eine konkrete Abwesenheit die gemessene Wiederaufheizenergie gegen das Heizen in der Pause rechnen — Compare matched heating sessions with and without an intervening pause.

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": {
      "pause_h": "<pause_h>",
      "weiter_kwh_h": "<weiter_kwh_h>",
      "langsamer_kwh_h": "<langsamer_kwh_h>",
      "wieder_kwh": "<wieder_kwh>",
      "gleiche_temperaturen": "<gleiche_temperaturen>"
    },
    "name": "heizpause_durchlaufen_wiederaufheizen"
  }
}

Input Schema

NameRequiredDescriptionDefault
pause_hYesGeplante Abwesenheit zwischen zwei Nutzungsblöcken in Stunden.
wieder_kwhYesZusätzliche gemessene Energie zur Wiederherstellung derselben Nutzungstemperatur.
weiter_kwh_hYesGemessener Verbrauch pro Stunde beim Weiterbetrieb während der Pause.
langsamer_kwh_hYesGemessener Verbrauch pro Stunde bei abgesenkter Einstellung während der Pause.
gleiche_temperaturenYesNutzungszustand zu Beginn und Ende sowie Außenbedingungen sind vergleichbar?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already establish readOnlyHint=true and openWorldHint=false, so safety is covered; the description adds that this is a paired comparison of measurements rather than a single-value lookup. However, with no output schema, it never states what the computation returns (energy delta, ratio, verdict), which is the main behavioral unknown for an agent.

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 stating the purpose plus a compact English gloss; nothing is padding. The bilingual duplication costs a little length but aids disambiguation for a German-named tool, so waste is minimal.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This dimension is context-weighted rather than a strict gap check; the tool has 5 fully documented required parameters, no nesting, and no output schema to explain. The description supplies the comparison framing the schema cannot, leaving nothing an agent needs in order to call it correctly.

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 at field level; baseline 3 applies. The description only loosely reinforces the meaning of pause_h ("konkrete Abwesenheit") and gleiche_temperaturen ("matched sessions") without adding units, tolerances, or validity rules 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 definition names a specific operation (rechnen/compare) on specific quantities (gemessene Wiederaufheizenergie vs. Heizen in der Pause) for a concrete absence period, so an agent knows exactly what is being computed. It is clear without needing sibling differentiation, since the listed siblings belong to unrelated domains.

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?

"Für eine konkrete Abwesenheit" implies the usage context (a single, defined absence between two usage blocks) and "matched heating sessions" hints at the comparability precondition. There is no explicit when-not guidance, no mention of what to do when sessions are not matched, and no named alternative tool.

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