Skip to main content
Glama

getecoback-climate-weather

punktwaerme_temperaturdefizit_linie_abschnitt

Read-only

Bei linear angenähertem Kurzverlauf die Fläche unterhalb des eigenen Wärmeziels während tatsächlicher Nutzung berechnen — Integrate only below-target deficit across one occupied segment.

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": {
      "anfang_c": "<anfang_c>",
      "ende_c": "<ende_c>",
      "mindestziel_c": "<mindestziel_c>",
      "dauer_min": "<dauer_min>",
      "linear_plausibel": "<linear_plausibel>"
    },
    "name": "punktwaerme_temperaturdefizit_linie_abschnitt"
  }
}

Input Schema

NameRequiredDescriptionDefault
ende_cYesTemperatur am Ende desselben Abschnitts.
anfang_cYesTemperatur zum Beginn des kurzen tatsächlich belegten Abschnitts.
dauer_minYesDauer des aufgezeichneten Abschnitts in Minuten.
mindestziel_cYesEigenes Minimum für dieselbe Messgröße.
linear_plausibelYesIst die lineare Näherung im betrachteten Abschnitt überprüft und für diesen Zweck vertretbar?

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

The annotations already establish that this is a read-only, closed-world operation. The description adds useful scope details, such as integrating only below-target deficit and only across one occupied segment, but it does not explain output units, sign conventions, or behavior when the linear approximation is not plausible.

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?

The definition is short and front-loads the condition and core calculation. The bilingual restatement is slightly redundant but still efficient overall.

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 calculation tool with no output schema, the description covers the core concept but does not specify the return value in detail, such as units or how above-target periods are handled. The required linear_plausibel parameter and the behavior when it is false also remain unexplained.

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 in the input schema. The description adds conceptual framing around below-target deficit and occupied segments, but it does not add parameter-specific semantics beyond what the schema provides.

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 states a specific calculation: area below the own heat target during actual use, restricted to one occupied segment with a linear approximation. It is clear what the tool computes, though it does not explicitly differentiate itself from sibling tools.

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?

The description implies when the tool applies: a linearly approximated short profile, actual occupancy, and a single segment. It does not state when not to use the tool, name alternatives, or explain the role of the required linear_plausibel check.

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