Skip to main content
Glama

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

Estrich Menge berechnen

bot_026
Read-onlyIdempotent

[Markt: CH/DE | Norm: Fachformel ohne Normbezug] Estrich Menge berechnen: berechnet Benötigtes Frischmörtelvolumen [m³]; Gesamtgewicht Estrichmörtel [kg]; Anzahl Säcke rechnerisch (unaufgerundet) [Sack]; Benötigte Anzahl Säcke (ganze Säcke) [Sack]. WANN VERWENDEN: Wenn Benötigtes Frischmörtelvolumen für diese Aufgabe orientierend bestimmt oder ein Angebot beziehungsweise eine Auslegung plausibilisiert werden soll. EINGABEN: Fläche [m²] (1–1000); Estrichdicke [mm] (20–200); Frischmörteldichte [kg/m³] (1500–2500); Gewicht pro Sack [kg] (5–50); Verschnitt- und Reservezuschlag [%] (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_026"
  }
}

Input Schema

NameRequiredDescriptionDefault
dichteNoFrischmörteldichte [kg/m³], 1500–2500
regionNoDE = Deutschland/Österreich (DIN VDE, eBay.de), CH = Schweiz (NIN/SIA, eBay.ch)DE
flaecheNoFläche [m²], 1–1000
verschnittNoVerschnitt- und Reservezuschlag [%], 0–30
sackgewichtNoGewicht pro Sack [kg], 5–50
estrichdickeNoEstrichdicke [mm], 20–200

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 declare readOnlyHint, idempotentHint and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavioral context: the result is a non-binding preliminary estimate, valid only within the stated input ranges, and carries no pricing or availability information. It does not describe rounding behavior beyond the output labels, which is a minor gap.

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 text is front-loaded with market/norm tags, then purpose, then labeled WANN/EINGABEN/GRENZEN blocks, which makes it scannable. It is dense and somewhat repetitive with the schema on the input ranges, but no sentence is pure filler.

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 fully enumerates the returned quantities with units, and it states the validity envelope and disclaimers. For a read-only calculator with six optional parameters, an agent has everything needed to call it and interpret the result.

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 every parameter is already documented with unit and range in the schema. The description restates the same ranges (Fläche 1–1000, Dicke 20–200, Dichte 1500–2500, Sackgewicht 5–50, Verschnitt 0–30) without adding semantics such as how Verschnitt is applied. The 'region' parameter is only hinted at via the '[Markt: CH/DE]' tag, so the baseline 3 is appropriate.

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 ('Estrich Menge berechnen') and enumerates the four computed outputs with units (Frischmörtelvolumen [m³], Gesamtgewicht [kg], Säcke rechnerisch, ganze Säcke). It cannot differentiate from siblings because the sibling names (bot_009, bot_010, …) are opaque identifiers, so full marks for differentiation are not achievable.

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 clear condition: use when the fresh-mortar volume is to be estimated roughly or an offer/design is to be plausibility-checked. 'GRENZEN' adds explicit exclusions (no execution planning, no norm acceptance, no prices or deliverability). No named alternative tool is offered, which keeps it below 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