Skip to main content
Glama

getecoback-climate-weather

klima_waermeabgabe_kreislauf

Read-only

Abgeführte Wärme und elektrische Aufnahme zu einer idealen Warmseitenbilanz zusammenführen — Estimate hot-side heat rejection from matched cooling capacity and electrical input.

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": {
      "kaelteleistung_w": "<kaelteleistung_w>",
      "aufnahme_w": "<aufnahme_w>",
      "gleicher_betriebspunkt": "<gleicher_betriebspunkt>"
    },
    "name": "klima_waermeabgabe_kreislauf"
  }
}

Input Schema

NameRequiredDescriptionDefault
aufnahme_wYesElektrische Aufnahme der bilanzierten Einheit in Watt am gleichen Betriebspunkt.
kaelteleistung_wYesVom Kältekreislauf abgeführte Nutzwärme in Watt am angegebenen Betriebspunkt.
gleicher_betriebspunktYesLeistungswerte gleichzeitig oder aus demselben Hersteller-Prüfpunkt?

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 declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered and the description only needs to add calculation context, which it does by framing the operation as a warm-side energy balance. However, it says nothing about the returned quantity's unit, whether the result is an estimate versus a strict equality, or how the tool reacts when the operating-point flag is false.

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 operation before the English restatement. The German and English sentences convey essentially the same content, making the second sentence partly redundant, but no significant padding exists.

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 simple three-parameter calculation with full schema coverage and read-only annotations, the essentials are present. Still, with no output schema the description should clarify what is returned (presumably a watt value) and what happens if gleicher_betriebspunkt is false, both of which are left unstated.

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 schema already defines all three parameters in detail, and the baseline of 3 applies. The description reinforces the conceptual pairing of cooling capacity with electrical input but adds no formatting, unit, or validation detail 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 description names a concrete computation: combining rejected heat and electrical input into an ideal hot-side balance to estimate heat rejection from cooling capacity plus electrical input. This is a specific verb-and-resource statement an agent can act on, though it does not explicitly contrast itself with nearby siblings such as klima_kuehlleistung_einheit_abgleich or klima_nachstroemwaerme_schaetzen.

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?

Usage is only implied by the phrase 'matched cooling capacity and electrical input', which hints that consistent operating-point data is required, but there is no explicit when-to-use, when-not-to-use, or named alternative tool. The agent must infer applicability from the purpose statement alone.

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