Skip to main content
Glama

getecoback-raumklima

heizverlauf_restwinter_gleiche_jahresphase

Read-only

Einen bereits gemessenen Teil der Heizsaison und einen getrennten Rest aus einem belegten Vorjahresprofil einordnen — Back a remaining-season heat scenario with a separately matched historical season share.

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": {
      "aktuell_bis_stichtag_kwh": "<aktuell_bis_stichtag_kwh>",
      "vorjahr_bis_stichtag_kwh": "<vorjahr_bis_stichtag_kwh>",
      "vorjahr_rest_kwh": "<vorjahr_rest_kwh>",
      "fortschreiben": "<fortschreiben>",
      "basis_passend": "<basis_passend>"
    },
    "name": "heizverlauf_restwinter_gleiche_jahresphase"
  }
}

Input Schema

NameRequiredDescriptionDefault
basis_passendYesSind wiederkehrende Heizaufgaben, Zeitgrenzen und Herkunft beider Teile ausreichend vergleichbar?
fortschreibenYesSoll dieselbe beobachtete Abweichungsquote auch für den Rest als ausdrückliche Annahme verwendet werden?
vorjahr_rest_kwhYesVorjahreswärme ab dieser Saisonstelle bis Saisonende.
aktuell_bis_stichtag_kwhYesAktuell beobachtete Wärmemenge bis zum gemeinsamen Saisonstichtag.
vorjahr_bis_stichtag_kwhYesVorjahreswärme bis exakt zur vergleichbaren Saisonstelle.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.5/5.0
Behavior2/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. Beyond that, the description does not explain what the computation actually produces (a scenario value, a comparison, a projection?) and never mentions the 'fortschreiben' assumption's effect. With no output schema, this silence leaves real behavioral gaps.

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

Conciseness3/5

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

It is a short two-sentence definition with no padding, but the German/English duplication spends words restating rather than adding detail, and the front-loaded content is abstract. Adequate but not efficiently informative.

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

Completeness2/5

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

This is a read-only calculation with five fully documented params but no output schema, so the agent genuinely needs the description to say what comes back. The description instead restates the setup, leaving the return value and the meaning of the result 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 the five parameters are already documented in the schema. The description adds no extra meaning about how the measured share, rest share, and 'fortschreiben' combine, so the baseline 3 applies.

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

Purpose3/5

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

The description names the resource area (heating season measured share plus a separate rest from a prior-year profile) and a verb, 'einordnen' / 'Back a scenario.' But 'einordnen' is abstract and the phrase 'back a remaining-season heat scenario' is hard to pin to a concrete operation, so the agent understands the topic more than the action. It does not clearly distinguish itself from the many other heizverlauf siblings.

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 statement of when to use this tool, no when-not conditions, and no named alternative among the many heizverlauf_* siblings. The agent must infer the selection criteria entirely from the topic language.

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