Skip to main content
Glama

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

Rechter Winkel & Diagonalen-Rechner

bot_056
Read-onlyIdempotent

[Markt: CH/DE | Norm: Fachformel ohne Normbezug] Rechter Winkel & Diagonalen-Rechner: berechnet Soll-Diagonale für exakt 90° c_soll [m]; Seite b aus a und gemessener Diagonale [m]; Fläche A = a·b [m²]; Umfang U = 2·(a + b) [m]. WANN VERWENDEN: Wenn Soll-Diagonale für exakt 90° c_soll für diese Aufgabe orientierend bestimmt oder ein Angebot beziehungsweise eine Auslegung plausibilisiert werden soll. EINGABEN: Seite a (Länge) [m] (0.1–200); Seite b (Breite) [m] (0.1–200); Gemessene Diagonale c_ist (Maßband / Laser) [m] (0.1–300). 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_056"
  }
}

Input Schema

NameRequiredDescriptionDefault
aNoSeite a (Länge) [m], 0.1–200
bNoSeite b (Breite) [m], 0.1–200
c_istNoGemessene Diagonale c_ist (Maßband / Laser) [m], 0.1–300
regionNoDE = Deutschland/Österreich (DIN VDE, eBay.de), CH = Schweiz (NIN/SIA, eBay.ch)DE

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful context beyond that: the input validity envelope (gültig nur im angegebenen Eingabebereich), the non-binding disclaimer, and the market/norm framing — this tells the agent the output is an indicative pre-dimensioning rather than a certified result.

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 front-loaded with market/norm tags and the tool name, then structured into formula, WANN VERWENDEN, EINGABEN and GRENZEN blocks, so an agent can scan it quickly. It is on the long side and repeats input ranges verbatim from the schema, which is the main wasted text.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a four-parameter, no-output-schema calculator, the definition covers what is computed, the valid input domain, and the limits of applicability. The only residual ambiguity is that b is described both as an input and as something derived from a and c_ist, which an agent must resolve from 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 all four parameters including the DE/CH region enum are already documented in the schema itself. The description restates the same three inputs with the same ranges, adding no new semantics such as units handling, tolerances for c_ist, or how b interacts with a measured diagonal — the baseline 3 applies.

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 computation domain and enumerates exactly what is produced: c_soll for an exact 90° angle, b derived from a plus the measured diagonal, area A = a·b and perimeter U = 2·(a + b). An agent can tell immediately that this is a right-angle/diagonal calculator rather than a generic geometry or tariff 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?

A dedicated 'WANN VERWENDEN' block states the intended context (orientierend bestimmen or plausibilisieren of an Angebot/Auslegung), and 'GRENZEN' explicitly excludes Ausführungsplanung, Normabnahme, prices and availability. What is missing is any reference to an alternative tool when the task is a different geometry problem, so the agent gets clear when-to-use but no routing to siblings.

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