Skip to main content
Glama

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

Druckverlust in Rohrleitungen berechnen

bot_065
Read-onlyIdempotent

[Markt: CH/DE | Norm: Fachformel ohne Normbezug] Druckverlust in Rohrleitungen berechnen: berechnet Strömungsgeschwindigkeit [m/s]; Reynolds-Zahl; Rohrreibungszahl (lambda); Druckverlust [bar]. WANN VERWENDEN: Wenn Strömungsgeschwindigkeit für diese Aufgabe orientierend bestimmt oder ein Angebot beziehungsweise eine Auslegung plausibilisiert werden soll. EINGABEN: Rohrlänge [m] (1–5000); Innendurchmesser [mm] (5–1000); Volumenstrom [m³/h] (0.1–1000); Dichte des Mediums [kg/m³] (500–1500); Rohrrauigkeit [mm] (0.001–5). 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_065"
  }
}

Input Schema

NameRequiredDescriptionDefault
regionNoDE = Deutschland/Österreich (DIN VDE, eBay.de), CH = Schweiz (NIN/SIA, eBay.ch)DE
rohrlangeNoRohrlänge [m], 1–5000
volumenstromNoVolumenstrom [m³/h], 0.1–1000
dichte_mediumNoDichte des Mediums [kg/m³], 500–1500
rohrrauigkeitNoRohrrauigkeit [mm], 0.001–5
rohrdurchmesserNoInnendurchmesser [mm], 5–1000

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish readOnly/idempotent/closed-world safety, and the description adds genuinely non-obvious behavioral context: the result is an unverbindliche Vorbemessung, uses a Fachformel ohne Normbezug, and is valid only inside the stated input ranges. It does not describe precision, rounding, or result structure beyond the four named quantities, which keeps it from a 5.

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 three labelled blocks (scope header, WANN VERWENDEN, EINGABEN, GRENZEN) make it easy to scan and the purpose is front-loaded. The EINGABEN sentence duplicates ranges that the schema already carries verbatim, which is the main piece of text that does not earn its place.

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 listing exactly which quantities are returned and in which units. Combined with the stated domain limits and the disclaimer about non-binding results, 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 the EINGABEN block merely restates the units and min/max ranges already present on every property — little value added. The 'region' parameter (enum DE/CH) is not explained at all in the description, leaving unanswered whether it changes the formula or only the market labelling.

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 names a specific verb and resource ('Druckverlust in Rohrleitungen berechnen') and enumerates the intermediate results produced (Strömungsgeschwindigkeit [m/s], Reynolds-Zahl, Rohrreibungszahl lambda, Druckverlust [bar]). It does not differentiate itself from any sibling, which is understandable given the opaque bot_NNN sibling names, so it lands at clear-but-not-differentiating rather than 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?

'WANN VERWENDEN' gives a concrete usage context (orientierende Bestimmung der Strömungsgeschwindigkeit, Plausibilisierung eines Angebots/einer Auslegung) and 'GRENZEN' explicitly excludes Ausführungsplanung, Normabnahme and Preis-/Lieferbarkeitsfragen. What is missing is any reference to an alternative tool for those excluded tasks, 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