Skip to main content
Glama

getecoback-climate-weather

heizprotokoll_komfort_erfuellung_vergleich

Read-only

Heizenergie nur gemeinsam mit tatsächlich erreichten Komfortstunden vor und nach einer Änderung vergleichen — Check whether lower heating energy came with reduced hours meeting the same target.

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": {
      "a_kwh": "<a_kwh>",
      "b_kwh": "<b_kwh>",
      "a_ziel_stunden": "<a_ziel_stunden>",
      "b_ziel_stunden": "<b_ziel_stunden>",
      "ziel_dauer_stunden": "<ziel_dauer_stunden>",
      "gleicher_messort": "<gleicher_messort>"
    },
    "name": "heizprotokoll_komfort_erfuellung_vergleich"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_kwhYesWärmeenergie im vollständigen früheren Fenster.
b_kwhYesWärmeenergie im vollständigen späteren gleich langen Fenster.
a_ziel_stundenYesFrühere belegte Stunden, in denen das selbst gewählte Zielband eingehalten wurde.
b_ziel_stundenYesSpätere belegte Stunden, in denen dasselbe Zielband eingehalten wurde.
gleicher_messortYesGleiches Zielband, gleicher Messort und gleichwertige Erfassung belegt?
ziel_dauer_stundenYesGleiche Dauer der tatsächlich relevanten Belegungsstunden in beiden Zeitfenstern.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered; the description adds the substantive behavioral stance that the tool refuses to treat energy savings as meaningful without a comfort-hours check. It does not state whether the tool rejects inputs when gleicher_messort is false or how it flags non-comparability.

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 no filler, and the core caveat (energy only in conjunction with achieved comfort hours) is front-loaded before the gloss. The bilingual packaging is slightly redundant but not wasteful.

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 six-parameter, all-required comparator with no output schema, the definition states what is compared and the comparability precondition but says nothing about the result (difference, normalization by window length, or a warning when conditions mismatch). An agent knows when to call it but not what it will receive.

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 German field descriptions already define each of the six inputs, including the 'same measurement location' attestation. The description only reinforces the intent of the paired energy and target-hour values, adding no additional format or range semantics beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific comparison operation (heating energy vs. actually achieved comfort hours, before and after a change) and states the guardrail: energy may only be judged together with hours meeting the same target. That verb+resource+scope is precise enough to separate it from the sibling *_vergleich tools, which each cover different quantities.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It specifies the condition under which comparison is legitimate (same target band, same measurement location, comparable recording, equal window length) and frames the question it answers: did lower energy come with fewer compliant hours? It does not explicitly say what to do when the setup is not comparable or which tool to use instead.

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