Skip to main content
Glama

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

Heizlast in kWh umrechnen: Energiemenge berechnen

bot_017
Read-onlyIdempotent

[Markt: CH/DE | Norm: Fachformel ohne Normbezug] Heizlast in kWh umrechnen: Energiemenge berechnen: berechnet Jahresenergie [kWh/a]; Monatsenergie (Durchschnitt) [kWh/Monat]; Tagesenergie (Durchschnitt) [kWh/Tag]. WANN VERWENDEN: Wenn Jahresenergie für diese Aufgabe orientierend bestimmt oder ein Angebot beziehungsweise eine Auslegung plausibilisiert werden soll. EINGABEN: Heizlast [kW] (0.5–50); Volllaststunden pro Jahr [h/a] (1–8760). 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_017"
  }
}

Input Schema

NameRequiredDescriptionDefault
regionNoDE = Deutschland/Österreich (DIN VDE, eBay.de), CH = Schweiz (NIN/SIA, eBay.ch)DE
heizlast_kwNoHeizlast [kW], 0.5–50
volllaststundenNoVolllaststunden pro Jahr [h/a], 1–8760

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and closed-world, and the description adds real context beyond them: the result is a non-binding preliminary sizing based on a 'Fachformel ohne Normbezug' and is only valid inside the stated input ranges. That tells the agent how much to trust the numbers, which annotations alone cannot convey. Return format is described only at the level of output quantity names.

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 labeled structure (market/norm header, WANN VERWENDEN, EINGABEN, GRENZEN) is front-loaded and easy to scan, with no filler sentences. Minor waste comes from repeating the tool name/title verbatim at the start of the description and from restating input ranges already in the schema.

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 three returned quantities and their units, and it discloses the non-binding scope plus the market/norm disclaimer. What is missing is any mention of the region switch and its effect, which matters for a CH/DE tool. Otherwise nothing an agent needs to invoke it correctly is absent.

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 coverage is 100%, so the baseline is 3. The description restates the two numeric inputs with their ranges but adds no syntax, defaults or interpretation beyond the schema, and it never mentions the 'region' parameter (DE/CH with its DIN VDE vs NIN/SIA implication).

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 computation: annual, monthly (average) and daily (average) energy in kWh derived from Heizlast and full-load hours, with units for each output. This is far more than a restatement of the name and lets an agent understand exactly what is produced. It does not differentiate against the many opaque sibling tools (bot_009…bot_067), so it stops short of a 5.

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?

An explicit 'WANN VERWENDEN' block says to use it when annual energy is to be estimated or an offer/design is to be plausibility-checked, and 'GRENZEN' rules out execution planning, norm certification, prices and availability. The guidance is clear, but no named alternative tool is offered for the excluded cases.

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