Skip to main content
Glama

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

Holz-Carport / Pergola: Vordimensionierung der Sparren

simulate_timber_carport_statik
Read-onlyIdempotent

[Markt: CH/DE | Norm: Eurocode 5 (DE), CH: konservative Reserve 0,85, kein SIA-265-Nachweis] Vordimensionierung eines Holz-Carports: Sparren, Pfette, Stuetzen, Schneelast aus PLZ, Windsog als Kennwert. WANN VERWENDEN: Bei Fragen zur Tragfaehigkeit von Carport-Sparren. EINGABEN: plz, l_sp (Spannweite [m]), b_s (Sparrenbreite [mm]), h_s (Sparrenhoehe [mm]). GRENZEN: Vordimensionierung, kein statischer Nachweis (Wind, Aussteifung, Verbindungen, Fundamente nicht geprueft).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "plz": "<plz>",
      "l_sp": "<l_sp>",
      "b_s": "<b_s>",
      "h_s": "<h_s>"
    },
    "name": "simulate_timber_carport_statik"
  }
}

Input Schema

NameRequiredDescriptionDefault
b_sYes
h_sYes
plzYes
l_spYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Beyond the annotations (readOnly/openWorld/idempotent, which are consistent with a pure calculation), the description discloses the governing standard (Eurocode 5, no SIA-265), a CH-specific conservative reserve of 0.85, that snow load is derived from the postal code, and that wind suction is only a characteristic value. It does not say what the calculation actually returns, which is the remaining behavioral 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 bracketed market/norm header, the use-case line, the input list and the limits line are each front-loaded and labelled, so an agent can scan to the part it needs. The density is high and no sentence is pure filler, though the norm header block is heavy relative to the rest.

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

Completeness3/5

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

For a domain-specific engineering calculation with no output schema, the definition covers norms, inputs, and scope limits well, but never indicates what the result looks like (utilization ratio, pass/fail, suggested dimensions). An agent knows when and how to call it but not what it will get back.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate, and it does: all four parameters are glossed with meaning and units (Spannweite [m], Sparrenbreite [mm], Sparrenhoehe [mm]), and crucially it explains that plz is used to derive the snow load — a semantic link the bare schema pattern does not convey. It stops short of noting the numeric ranges that the schema enforces.

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 opening sentence names a specific verb and object ('Vordimensionierung eines Holz-Carports: Sparren, Pfette, Stuetzen') and lists exactly which structural members and loads are covered. An agent can tell this is a preliminary sizing calculation for carport rafters, not a generic simulation, without opening the schema.

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 explicit 'WANN VERWENDEN' block ties use to questions about carport rafter load capacity, and the 'GRENZEN' block effectively states when the tool is not sufficient (no formal static verification, no wind/bracing/connection/foundation checks). What is missing is a pointer to an alternative tool for those excluded cases.

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