Skip to main content
Glama

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

Durchfluss berechnen in l/min

bot_027
Read-onlyIdempotent

[Markt: CH/DE | Norm: Fachformel ohne Normbezug] Durchfluss berechnen in l/min: berechnet Durchfluss (Volumenstrom) [l/min]; Durchfluss (Volumenstrom) [m³/h]. WANN VERWENDEN: Wenn Durchfluss (Volumenstrom) für diese Aufgabe orientierend bestimmt oder ein Angebot beziehungsweise eine Auslegung plausibilisiert werden soll. EINGABEN: Innendurchmesser des Rohrs [mm] (1–1000); Mittlere 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_027"
  }
}

Input Schema

NameRequiredDescriptionDefault
regionNoDE = Deutschland/Österreich (DIN VDE, eBay.de), CH = Schweiz (NIN/SIA, eBay.ch)DE
durchmesser_mmNoInnendurchmesser des Rohrs [mm], 1–1000
geschwindigkeit_m_sNoMittlere Strömungsgeschwindigkeit [m/s], 0.1–10

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the read-only and idempotent annotations, the description discloses important behavioral limits: it uses a technical formula without norm reference, is non-binding preliminary sizing, and is valid only within the stated input range. These caveats materially help an agent judge when the result is appropriate.

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 organized into purpose, usage, inputs, and limits sections with the key purpose front-loaded. There is minor redundancy in restating the title and output units, but it remains efficient overall.

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?

For a simple three-parameter calculator with no output schema, the description covers purpose, when to use it, inputs, output units, and important validity limits. The remaining parameter details are already fully covered by the schema.

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 the diameter, velocity, and region parameters in detail. The description repeats the diameter and velocity ranges but adds no meaning beyond the schema, so the baseline score of 3 applies.

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 states a specific action and resource: calculating volumetric flow rate in l/min and m³/h from pipe diameter and velocity. It is clear what the tool does, but it does not distinguish this calculator from any sibling tool.

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?

It explicitly says when to use the tool: for orienting flow-rate estimates or plausibility checks of an offer or design. It also states limits such as no execution planning or norm acceptance, though it does not name alternative tools.

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