Skip to main content
Glama

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

Rohrdurchmesser berechnen

bot_034
Read-onlyIdempotent

[Markt: CH/DE | Norm: Fachformel ohne Normbezug] Rohrdurchmesser berechnen: berechnet Erforderliche Querschnittsfläche [m²]; Erforderlicher Innendurchmesser [mm]. WANN VERWENDEN: Wenn Erforderliche Querschnittsfläche für diese Aufgabe orientierend bestimmt oder ein Angebot beziehungsweise eine Auslegung plausibilisiert werden soll. EINGABEN: Volumenstrom [m³/h] (0.1–1000); Strömungsgeschwindigkeit [m/s] (0.1–10). 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_034"
  }
}

Input Schema

NameRequiredDescriptionDefault
regionNoDE = Deutschland/Österreich (DIN VDE, eBay.de), CH = Schweiz (NIN/SIA, eBay.ch)DE
flow_m3hNoVolumenstrom [m³/h], 0.1–1000
velocity_msNoStrömungsgeschwindigkeit [m/s], 0.1–10

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/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, so safety is covered; the description adds real behavioral context beyond that: results are non-binding preliminary sizing, are only valid inside the stated input range, and carry no normative approval. It does not discuss rounding or precision of the returned values, 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 labeled sections (market/norm header, purpose, WANN VERWENDEN, EINGABEN, GRENZEN) put the most decision-relevant information first and leave no filler sentences. Minor redundancy between the EINGABEN ranges and the schema ranges costs a point but does not hurt readability.

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?

With no output schema, the description carries the burden of describing return values and does so precisely (cross-sectional area in m², inner diameter in mm). For a small three-parameter calculation tool with full annotation coverage, nothing an agent needs to invoke it correctly is missing.

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 both numeric parameters already carry units and ranges; the description's input line largely restates them. The third parameter, region (DE/CH enum), is not mentioned in the description at all and is only explained by the schema, so the description adds no meaning beyond structured data.

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 ("Rohrdurchmesser berechnen") and enumerates the exact outputs produced: required cross-sectional area in m² and required inner diameter in mm. The market/norm tag (CH/DE, Fachformel ohne Normbezug) further scopes what kind of calculation this is, so the agent knows it is a formula-based sizing tool, not a lookup.

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 the concrete situation (rough sizing of required cross-section, plausibility-checking an offer or design), and "GRENZEN" explicitly excludes execution planning, norm acceptance, and pricing/availability. It stops short of naming an alternative tool, but the sibling names are opaque IDs, so there is nothing meaningful to route to.

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