Skip to main content
Glama

getecoback-raumklima

nachtabsenkung_messvergleich

Read-only

Verbrauch vor und nach einem Heizzeitplan unter vergleichbaren Bedingungen auswerten — Compare heating-only meter readings before and after a schedule change.

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": {
      "before_kwh": "<before_kwh>",
      "after_kwh": "<after_kwh>",
      "before_days": "<before_days>",
      "after_days": "<after_days>",
      "comparable": "<comparable>"
    },
    "name": "nachtabsenkung_messvergleich"
  }
}

Input Schema

NameRequiredDescriptionDefault
after_kwhYesNur Raumheizung im Testzeitraum in kWh.
after_daysYesDauer des Testzeitraums in Tagen.
before_kwhYesNur Raumheizung im Ausgangszeitraum in kWh.
comparableYesWetter, Belegung und Heizkomfort waren vergleichbar und nur der Heizzeitplan wurde geändert.
before_daysYesDauer des Ausgangszeitraums in Tagen.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already establish that this is a read-only, closed-world operation. The description adds the important scope that only heating energy is compared and that conditions must be comparable, but it does not explain the calculation, result format, or assumptions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The definition is a single compact sentence, front-loading the purpose and scope. The German/English pairing is redundant but not wasteful, and no sentence is 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?

The purpose and input scope are clear, and annotations/schema cover safety and parameters. However, with no output schema, the definition does not say what comparison result is returned (e.g., savings, ratio, or diagnostic), leaving a meaningful gap for a calculation tool.

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 coverage is 100%, so all five parameters are fully described in the schema. The description reinforces 'heating-only' and comparable conditions but adds no parameter-level syntax, units, or constraints 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 uses a specific verb-resource combination ('Compare heating-only meter readings before and after a schedule change') and states the comparison scope explicitly. It distinguishes this from sibling measurement tools by restricting readings to heating-only consumption tied to a schedule change.

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 gives clear context for use: comparing consumption before and after a heating schedule change under comparable conditions. It does not name alternatives or explicit exclusions, but the condition 'unter vergleichbaren Bedingungen' provides a usable guideline.

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