Skip to main content
Glama

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

Wärmepumpe Stromverbrauch und Heizkosten berechnen

bot_049
Read-onlyIdempotent

[Markt: CH/DE | Norm: Fachformel ohne Normbezug] Wärmepumpe Stromverbrauch und Heizkosten berechnen: berechnet Gesamter Nutzwärmebedarf Q_ges [kWh/a]; Jahresstromverbrauch Wärmepumpe E_WP [kWh/a]; Jährliche Stromkosten [CHF/a]. WANN VERWENDEN: Wenn Gesamter Nutzwärmebedarf Q_ges für diese Aufgabe orientierend bestimmt oder ein Angebot beziehungsweise eine Auslegung plausibilisiert werden soll. EINGABEN: Jahres-Heizwärmebedarf Q_Heiz [kWh/a] (1000–100000); Jahres-Wärmebedarf Warmwasser Q_WW [kWh/a] (0–20000); Strompreis [CHF/kWh] (0.05–1); Jahresarbeitszahl JAZ (1.5–6). 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_049"
  }
}

Input Schema

NameRequiredDescriptionDefault
jazNoJahresarbeitszahl JAZ, 1.5–6
q_wwNoJahres-Wärmebedarf Warmwasser Q_WW [kWh/a], 0–20000
q_heizNoJahres-Heizwärmebedarf Q_Heiz [kWh/a], 1000–100000
regionNoDE = Deutschland/Österreich (DIN VDE, eBay.de), CH = Schweiz (NIN/SIA, eBay.ch)DE
strompreisNoStrompreis [CHF/kWh], 0.05–1

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / strompreis / description
      Previous value: -"Strompreis [/kWh], 0.05–1"New value: +"Strompreis [CHF/kWh], 0.05–1"
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/closed-world, so the description adds real value beyond them: it discloses the market scope (CH/DE), that the method is a Fachformel without norm reference, that results are non-binding preliminary sizing, and that validity is bounded by the stated input ranges. It does not describe rounding, units consistency for CHF vs. EUR, or error behaviour.

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?

Structure is strongly front-loaded with market/norm tags, then purpose, when-to-use, inputs and limits. The EINGABEN sentence largely duplicates schema content and could be dropped, but the rest earns its place.

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?

For a computational tool with no output schema, the description names the returned quantities and their units, plus the validity envelope. The notable omission is that all five parameters are optional with defaults — the agent is not told what happens when inputs are omitted or what the default scenario represents.

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 schema already documents all five parameters with ranges and defaults; the description merely repeats the four numeric inputs and their bounds. The 'region' parameter and its effect on markets/currency is not explained in the description at all, so no meaning is added beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/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 ('Wärmepumpe Stromverbrauch und Heizkosten berechnen') and enumerates the three concrete outputs: Q_ges [kWh/a], E_WP [kWh/a] and annual electricity costs [CHF/a]. An agent knows exactly what the tool returns before opening the schema, even though sibling tools are opaque identifiers.

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 an explicit trigger (orientierend bestimmen of Q_ges or plausibilisieren of an offer/Auslegung), and 'GRENZEN' states when-not (no Ausführungsplanung, no Normabnahme, no prices/availability). It lacks reference to named alternative tools, which is the only gap.

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