Skip to main content
Glama

getecoback-raumklima

heizkreis_waermeabgabe

Read-only

Wärmeleistung eines wassergeführten Heizkreises aus vorliegenden Messwerten abschätzen — Estimate water-loop heat delivery from recorded flow and temperature drop.

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": {
      "flow_l_hour": "<flow_l_hour>",
      "supply_c": "<supply_c>",
      "return_c": "<return_c>"
    },
    "name": "heizkreis_waermeabgabe"
  }
}

Input Schema

NameRequiredDescriptionDefault
return_cYesGemessener Rücklauf in °C.
supply_cYesGemessener Vorlauf in °C.
flow_l_hourYesGemessener Volumenstrom aus der Anlagenanzeige in l/h.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior3/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 meaningful qualifier that the result is an estimate derived from recorded measurements, but it omits the calculation basis (e.g. 1.163 · flow · ΔT), the output unit (W vs kW), and whether flow and temperatures must be sampled simultaneously. Useful framing, incomplete behavior.

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?

The content is short, but it is stated twice, once in German and once in English, so half the text is pure duplication. The purpose leads, which is good, but a single bilingual line would earn its place better than a mirrored pair.

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?

With only three fully documented parameters and no output schema, the agent still lacks the return unit and the approximation's assumptions (e.g. water heat capacity, steady-state flow). For a physics-calculation tool that produces a number the agent will report onward, that gap matters, though the read-only annotation keeps the risk low.

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% and all three parameters are required with ranges and units (°C, l/h) documented in the schema. The description's only added nuance is re-framing supply/return as a 'temperature drop', hinting that their difference drives the result; that is marginal beyond the schema baseline of 3.

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 specific verb and resource: estimating ('abschätzen') the heat output ('Wärmeleistung') of a water-borne heating circuit ('wassergeführter Heizkreis'). It also names the inputs used, flow and temperature drop, which separates it from cousins like 'bauteil_waermeverlust' (loss) or 'heizleistung_watt' in spirit, though no sibling is named explicitly.

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?

The phrase 'aus vorliegenden Messwerten' / 'from recorded flow and temperature drop' implies the tool needs existing measurements, but there is no when-to-use guidance, no exclusions, and no pointer to an alternative among the many heating-related siblings. The agent must infer applicability on its own.

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