Skip to main content
Glama

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

Beton menge berechnen: Volumen in m³ und Masse

bot_025
Read-onlyIdempotent

[Markt: CH/DE | Norm: Fachformel ohne Normbezug] Beton menge berechnen: Volumen in m³ und Masse: berechnet Betonvolumen netto [m³]; Bestellmenge inkl. Verschnitt [m³]; Geschätzte Masse inkl. Verschnitt [t]. WANN VERWENDEN: Wenn Betonvolumen netto für diese Aufgabe orientierend bestimmt oder ein Angebot beziehungsweise eine Auslegung plausibilisiert werden soll. EINGABEN: Länge [m] (0.1–100); Breite [m] (0.1–100); Dicke (Bauteilstärke) [m] (0.01–3); Verschnittzuschlag [%] (0–30). 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_025"
  }
}

Input Schema

NameRequiredDescriptionDefault
regionNoDE = Deutschland/Österreich (DIN VDE, eBay.de), CH = Schweiz (NIN/SIA, eBay.ch)DE
width_mNoBreite [m], 0.1–100
length_mNoLänge [m], 0.1–100
waste_pctNoVerschnittzuschlag [%], 0–30
thickness_mNoDicke (Bauteilstärke) [m], 0.01–3

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 the safety profile is covered. The description adds genuinely new behavioral context: the formula has no normative basis, results are non-binding, and validity is restricted to the stated input ranges.

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 structure (market/norm header, outputs, WANN VERWENDEN, EINGABEN, GRENZEN) is easy to scan, and the output list is front-loaded. The only waste is the verbatim repetition of the title before the output enumeration.

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, yet the description explicitly names all three returned values with units, plus input bounds and disclaimers. For a single-purpose calculator with no required parameters, nothing an agent needs to call or interpret it 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 coverage is 100%, so every parameter is already documented with title, unit, range, and default. The EINGABEN list restates those same units and ranges rather than adding meaning, and the region enum is only hinted at through the 'Markt: CH/DE' tag, so it does not exceed the baseline.

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 (Betonvolumen berechnen) and enumerates the three concrete outputs: net volume [m³], order quantity including waste [m³], and estimated mass [t]. An agent knows exactly what the tool returns, and the market/norm tag at the start further scopes it, even though the opaque bot_* siblings offer no basis for differentiation.

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 situation (orientierende Vorbemessung, plausibilisieren eines Angebots) and the 'GRENZEN' block rules out execution planning, norm acceptance, and pricing/deliverability. It stops short of naming an alternative tool, but with only opaque IDs there is no sibling 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