Skip to main content
Glama

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

Mindestvolumen Pufferspeicher aus Mindestlaufzeit berechnen

bot_046
Read-onlyIdempotent

[Markt: CH/DE | Norm: Fachformel ohne Normbezug] Mindestvolumen Pufferspeicher aus Mindestlaufzeit berechnen: berechnet Wärmemenge während der Mindestlaufzeit [kWh]; Mindestvolumen Pufferspeicher [Liter]. WANN VERWENDEN: Wenn Wärmemenge während der Mindestlaufzeit für diese Aufgabe orientierend bestimmt oder ein Angebot beziehungsweise eine Auslegung plausibilisiert werden soll. EINGABEN: Heizleistung der Wärmepumpe Q_N [kW] (1–100); Mindestlaufzeit des Verdichters t_min [min] (3–60); Zulässige Temperaturspreizung im Speicher Delta T [K] (2–20). 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_046"
  }
}

Input Schema

NameRequiredDescriptionDefault
q_nNoHeizleistung der Wärmepumpe Q_N [kW], 1–100
t_minNoMindestlaufzeit des Verdichters t_min [min], 3–60
regionNoDE = Deutschland/Österreich (DIN VDE, eBay.de), CH = Schweiz (NIN/SIA, eBay.ch)DE
delta_tNoZulässige Temperaturspreizung im Speicher Delta T [K], 2–20

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?

The annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so safety and side-effect behaviour are covered. The description adds genuinely useful context beyond that: results are a non-binding preliminary sizing valid only inside the stated input ranges, and the formula has no standard reference. It does not discuss output formatting or rounding, so it is solid but not rich.

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 bracketed market/standard header followed by WANN VERWENDEN, EINGABEN and GRENZEN is strongly front-loaded and scannable. Some content duplicates the schema ranges verbatim, which is mild waste, but nothing is confusing or padded.

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 returned quantities and their units. Inputs, validity domain and the non-binding nature of the result are all stated, which is enough for a small four-parameter calculation tool; only the region parameter's role is left unexplained.

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 schema already documents all four parameters including ranges and the region enum, and the description's 'EINGABEN' list largely repeats those ranges. The description also omits the region parameter entirely, leaving its effect (DE vs CH market conventions) to the schema, so it adds little meaning beyond structured data.

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 gives a specific verb and resource ('Mindestvolumen Pufferspeicher aus Mindestlaufzeit berechnen') and names both results, Wärmemenge [kWh] and Mindestvolumen [Liter], so the agent knows exactly what it gets back. It cannot differentiate itself from the sibling tools, but those are opaque bot_0xx identifiers with no described scope to contrast against, so the loss is minimal.

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 states a clear condition: use it when the heat quantity over the minimum runtime is to be estimated for this task or when an offer/design is to be plausibilised. The 'GRENZEN' block adds exclusions (no detailed design, no standard acceptance, no pricing), though it never names an alternative tool to use instead.

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