Skip to main content
Glama

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

Kabelquerschnitt in Durchmesser umrechnen

bot_043
Read-onlyIdempotent

[Markt: CH/DE | Norm: Fachformel ohne Normbezug] Kabelquerschnitt in Durchmesser umrechnen: berechnet Leiterdurchmesser [mm]; Leiterradius [mm]. WANN VERWENDEN: Wenn Leiterdurchmesser für diese Aufgabe orientierend bestimmt oder ein Angebot beziehungsweise eine Auslegung plausibilisiert werden soll. EINGABEN: Leiterquerschnitt [mm²] (0.5–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_043"
  }
}

Input Schema

NameRequiredDescriptionDefault
regionNoDE = Deutschland/Österreich (DIN VDE, eBay.de), CH = Schweiz (NIN/SIA, eBay.ch)DE
querschnitt_mm2NoLeiterquerschnitt [mm²], 0.5–300

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?

Annotations already cover read-only, idempotent, closed-world behavior, so the description only needs to add task-level caveats — and it does: non-binding pre-dimensioning, no execution planning, no standard acceptance, no prices or availability, validity only within the stated input range. The CH/DE market tag adds scoping context the annotations do not carry.

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?

Front-loaded with the purpose, then clearly labeled WANN/EINGABEN/GRENZEN sections, making it easy to scan. The bracketed market/norm prefix is slightly cryptic but short and informative rather than wasteful.

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?

With no output schema, the description correctly names the computed results and bounds the input range and the liability scope. A minor tension exists: the header says 'Fachformel ohne Normbezug' while the region parameter implies DIN VDE/NIN applicability, but this doesn't block correct invocation.

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 both parameters are documented in the schema, and the description's input note (Leiterquerschnitt 0.5–300 mm²) merely repeats it. The region parameter is not discussed in the description at all, so no meaning is added beyond the schema.

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?

States a concrete transformation (cross-section → conductor diameter) and names both outputs (Durchmesser [mm], Radius [mm]). Because the sibling tools are opaque IDs, no sibling differentiation is possible or needed; the description alone tells the agent exactly what the tool computes.

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 gives clear context: orientative determination of conductor diameter or plausibility-checking an offer/design. It does not name an alternative tool or an explicit when-not-to-use case, but given the opaque sibling names there is little concrete alternative to point at.

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