Skip to main content
Glama

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

U‑Wert Rechner für Dämmmaterialien

bot_018
Read-onlyIdempotent

[Markt: CH/DE | Norm: Fachformel ohne Normbezug] U‑Wert Rechner für Dämmmaterialien: berechnet U‑Wert [W/(m²·K)]. WANN VERWENDEN: Wenn U‑Wert für diese Aufgabe orientierend bestimmt oder ein Angebot beziehungsweise eine Auslegung plausibilisiert werden soll. EINGABEN: Wärmeleitfähigkeit des Materials [W/(m·K)] (0.01–1); Dämmstoffdicke [m] (0.01–0.5). 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_018"
  }
}

Input Schema

NameRequiredDescriptionDefault
regionNoDE = Deutschland/Österreich (DIN VDE, eBay.de), CH = Schweiz (NIN/SIA, eBay.ch)DE
lambda_w_mkNoWärmeleitfähigkeit des Materials [W/(m·K)], 0.01–1
thickness_mNoDämmstoffdicke [m], 0.01–0.5

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/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 behavior: the result is a non-binding preliminary estimate valid only inside the stated input range, with no price or availability implications. That is useful context an agent would otherwise lack.

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 market/norm tag, then purpose, then WHEN, then INPUTS, then LIMITS — a predictable, scannable structure. The INPUTS sentence is largely redundant with the schema's own titles and min/max bounds, which is the only wasted wording.

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 simple three-optional-parameter computation with no output schema, the description covers what is computed, the output unit, the validity domain and the liability limits. The one gap is that it never explains what the DE/CH region switch changes about the result, despite advertising a market-specific scope.

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% and the description only restates the lambda and thickness ranges already encoded as title/description/min/max in the schema. The region parameter (DE/CH enum, with its DIN/SIA meaning) is not addressed at all in the description, so no meaning is added beyond the structured fields.

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 result ('berechnet U-Wert [W/(m²·K)]' for insulation materials) plus a market/norm qualifier ('CH/DE | Fachformel ohne Normbezug'), so an agent knows exactly what computation it performs. It cannot differentiate against siblings because they are opaque bot_* names, which caps it at 4.

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?

An explicit 'WANN VERWENDEN' block describes the triggering situation (orientational determination or plausibility-checking an offer/design), and 'GRENZEN' states when the result must not be relied on (no execution planning, no norm acceptance, no pricing/availability). It stops short of naming an alternative tool for those excluded cases, so it is not a full 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