Skip to main content
Glama

https://fachrechner.com/api/v1/mcp

Heizleistung berechnen in kW

bot_024
Read-onlyIdempotent

[Markt: CH/DE | Norm: Fachformel ohne Normbezug] Heizleistung berechnen in kW: berechnet Thermische Heizleistung [kW]; Elektrische Anschlussleistung [kW]. WANN VERWENDEN: Wenn Thermische Heizleistung für diese Aufgabe orientierend bestimmt oder ein Angebot beziehungsweise eine Auslegung plausibilisiert werden soll. EINGABEN: Volumenstrom Wasser [l/min] (0.1–500); Temperaturdifferenz (Vorlauf minus Kaltwasser) [K] (0.1–100); Wirkungsgrad des Heizgeräts [%] (1–100). GRENZEN: Unverbindliche Vorbemessung (keine Ausführungsplanung, keine Normabnahme, keine Preise oder Lieferbarkeit; gültig nur im angegebenen Eingabebereich).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "bot_024"
  }
}

Input Schema

NameRequiredDescriptionDefault
regionNoDE = Deutschland/Österreich (DIN VDE, eBay.de), CH = Schweiz (NIN/SIA, eBay.ch)DE
wirkungsgrad_pctNoWirkungsgrad des Heizgeräts [%], 1–100
volumenstrom_l_minNoVolumenstrom Wasser [l/min], 0.1–500
temperaturdifferenz_kNoTemperaturdifferenz (Vorlauf minus Kaltwasser) [K], 0.1–100

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent and closed-world, so the safety profile is covered. The description adds real value beyond that by scoping validity to the stated input range and disclaiming norm acceptance, but it says nothing about the accuracy model, rounding, or how the two result values relate to each other.

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?

Labeled sections (Markt/Norm, WANN VERWENDEN, EINGABEN, GRENZEN) make it easy to scan and the purpose statement is front-loaded. The EINGABEN block largely duplicates ranges already in the schema, which is the main piece of low-value text.

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

Completeness4/5

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

With no output schema, the description correctly names the two outputs in kW, and it supplies scope, domain, and disclaimers appropriate for a small calculation tool. The one gap is the unexplained 'region' parameter, which implies a market/norm variant whose effect on the calculation is not described.

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 baseline is 3; the description merely restates the three input ranges already present in the schema and adds no format or interpretation guidance. Notably it never mentions the 'region' parameter (enum DE/CH) that also exists in the schema, leaving that input entirely to 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?

States a specific verb and resource ('Heizleistung berechnen in kW') and names both resulting quantities (thermische Heizleistung [kW], elektrische Anschlussleistung [kW]). It does not distinguish itself from any sibling, though the sibling names here are opaque identifiers that offer no basis for differentiation, so the ceiling is effectively 4.

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?

The 'WANN VERWENDEN' block gives a clear trigger condition (orientierende Bestimmung der Heizleistung, Plausibilisierung eines Angebots/einer Auslegung), and 'GRENZEN' states what it is not for (Ausführungsplanung, Normabnahme, Preise/Lieferbarkeit). It never names an alternative tool for the excluded cases, so it stops short of a 5.

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