Skip to main content
Glama

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

Wallbox kW Bedarf berechnen

bot_062
Read-onlyIdempotent

[Markt: CH/DE | Norm: NIN] Wallbox kW Bedarf berechnen: berechnet Benötigte Ladeleistung [kW]. WANN VERWENDEN: Wenn Benötigte Ladeleistung für diese Aufgabe orientierend bestimmt oder ein Angebot beziehungsweise eine Auslegung plausibilisiert werden soll. EINGABEN: Akkukapazität des Fahrzeugs [kWh] (10–150); Gewünschte Ladezeit [Stunden] (1–24); Geschätzter Wirkungsgrad [%] (70–100). 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_062"
  }
}

Input Schema

NameRequiredDescriptionDefault
regionNoDE = Deutschland/Österreich (DIN VDE, eBay.de), CH = Schweiz (NIN/SIA, eBay.ch)DE
efficiencyNoGeschätzter Wirkungsgrad [%], 70–100
charge_timeNoGewünschte Ladezeit [Stunden], 1–24
battery_capacityNoAkkukapazität des Fahrzeugs [kWh], 10–150

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 readOnly, idempotent and closed-world, so safety is covered. The description adds genuinely new behavioral context: results are unverbindliche Vorbemessung and only valid inside the stated input range, which tells the agent not to over-trust the output.

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?

Labeled sections (scope, WANN VERWENDEN, EINGABEN, GRENZEN) make it scannable and front-loaded. The EINGABEN block largely repeats the schema ranges, which is the only wasted text in an otherwise dense definition.

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, all-optional, read-only calculation with no output schema, the description covers purpose, validity envelope and limits. It does not state the return shape beyond the implied kW figure, but that is a minor gap for a pure computation.

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 units and ranges for efficiency, charge_time and battery_capacity are already fully documented. The description restates those ranges rather than adding meaning, and it says nothing extra about how 'region' changes the computation. Baseline 3 applies.

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 ('berechnet Benötigte Ladeleistung [kW]') and scopes it by market and norm (CH/DE, NIN). It cannot differentiate from the opaque bot_NNN siblings, but the calculation is unmistakable from the text alone.

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 states the triggering condition (orientierende Bestimmung der Ladeleistung, Plausibilisierung eines Angebots oder einer Auslegung). The 'GRENZEN' block adds explicit when-not conditions (keine Ausführungsplanung, keine Normabnahme, keine Preise/Lieferbarkeit). No alternative tool is named, which keeps it short of 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