Skip to main content
Glama

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

Heizstab im Warmwasserspeicher: Aufheizzeit und Stromverbrauch berechnen

bot_048
Read-onlyIdempotent

[Markt: CH/DE | Norm: Fachformel ohne Normbezug] Heizstab im Warmwasserspeicher: Aufheizzeit und Stromverbrauch berechnen: berechnet Erforderliche Wärmeenergie Q [kWh]; Elektrische Energie E_el [kWh]; Aufheizzeit t [h]. WANN VERWENDEN: Wenn Erforderliche Wärmeenergie Q für diese Aufgabe orientierend bestimmt oder ein Angebot beziehungsweise eine Auslegung plausibilisiert werden soll. EINGABEN: Speicherinhalt V [Liter] (30–2000); Anfangstemperatur T1 [°C] (5–70); Solltemperatur T2 [°C] (20–95); Leistung Heizstab P_el [kW] (0.5–12); Wirkungsgrad eta [%] (80–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_048"
  }
}

Input Schema

NameRequiredDescriptionDefault
t1NoAnfangstemperatur T1 [°C], 5–70
t2NoSolltemperatur T2 [°C], 20–95
etaNoWirkungsgrad eta [%], 80–100
p_elNoLeistung Heizstab P_el [kW], 0.5–12
regionNoDE = Deutschland/Österreich (DIN VDE, eBay.de), CH = Schweiz (NIN/SIA, eBay.ch)DE
volumenNoSpeicherinhalt V [Liter], 30–2000

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

The annotations already declare readOnly, idempotent and closed-world, so the safety profile is covered structurally. The description adds useful behavioral context: results are unverbindliche Vorbemessung and only valid within the stated input ranges. It does not say what happens with out-of-range inputs or how rounding/units are reported, so it goes beyond annotations but not far.

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 description is front-loaded with market/standard context, then purpose, usage, inputs and limits in clearly labeled segments, which is easy to scan. The input enumeration largely duplicates the schema and could be trimmed, but it is not verbose for a parametric calculation tool.

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

Completeness5/5

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

There is no output schema, and the description compensates by naming the three computed result quantities with units. Combined with the scope limits and market/standard qualifiers, an agent has everything needed to decide to call it and to interpret the answer.

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 all six parameters including the DE/CH enum are already documented in the schema. The 'EINGABEN' block restates the same parameters with the same ranges and units, adding no semantic detail beyond the schema; the only extra hint is the validity restriction to the given input range. Baseline 3 is appropriate.

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 uses a concrete verb and resource ('Heizstab im Warmwasserspeicher: Aufheizzeit und Stromverbrauch berechnen') and enumerates the three returned quantities (Q [kWh], E_el [kWh], t [h]), so an agent knows exactly what it computes. It does not distinguish itself from the sibling tools, though the siblings are all opaque bot_XXX identifiers, so differentiation is effectively impossible from the text alone.

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 use condition (orientierende Bestimmung von Q bzw. Plausibilisierung eines Angebots oder einer Auslegung), and the 'GRENZEN' block explicitly excludes Ausführungsplanung, Normabnahme, Preise und Lieferbarkeit. No alternative tool is named as a routing target, which keeps it from 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