Skip to main content
Glama

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

kWh Verbrauch berechnen

bot_050
Read-onlyIdempotent

[Markt: CH/DE | Norm: Fachformel ohne Normbezug] kWh Verbrauch berechnen: berechnet Energieverbrauch pro Tag [kWh]; Energieverbrauch pro Monat [kWh]; Energieverbrauch pro Jahr [kWh]; Stromkosten pro Monat [CHF]. WANN VERWENDEN: Wenn Energieverbrauch pro Tag für diese Aufgabe orientierend bestimmt oder ein Angebot beziehungsweise eine Auslegung plausibilisiert werden soll. EINGABEN: Leistung des Geräts [W] (1–10000); Betriebsstunden pro Tag [h] (0–24); Betriebstage pro Monat [Tage] (1–31); Strompreis [CHF/kWh] (0–2). 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_050"
  }
}

Input Schema

NameRequiredDescriptionDefault
regionNoDE = Deutschland/Österreich (DIN VDE, eBay.de), CH = Schweiz (NIN/SIA, eBay.ch)DE
power_wNoLeistung des Geräts [W], 1–10000
tariff_chfNoStrompreis [CHF/kWh], 0–2
hours_per_dayNoBetriebsstunden pro Tag [h], 0–24
days_per_monthNoBetriebstage pro Monat [Tage], 1–31

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/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 that results are non-binding preliminary estimates valid only inside the stated input range and carry no normative basis, which is genuine extra context, but it does not clarify error behavior or rounding/units of the returned values.

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 header and the WANN/GENZEN/EINGABEN structure make it easy to scan and front-load the purpose. The 'EINGABEN' sentence repeats ranges already in the schema, which is some redundancy but minor.

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, listing the four returned metrics is necessary and present, and the bounding disclaimer covers the tool's simulated/estimative nature. An agent has everything needed to call it correctly, though the effect of the region parameter on the results could be spelled out more.

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 five parameters with ranges and defaults are already documented. The description restates the same ranges and adds only the region framing (CH/DE market and normative context) in the header, which is marginal added meaning.

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?

States a specific verb and resource ('kWh Verbrauch berechnen') and enumerates the exact outputs (kWh per day/month/year plus monthly CHF cost), which is more precise than the title alone. It cannot differentiate itself against the opaque bot_0xx siblings by design, which keeps it just short of a 5.

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 a concrete application context (rough sizing of daily consumption, plausibility-checking an offer or design), and 'GRENZEN' explicitly excludes execution planning, norm approval, pricing and availability queries. It stops short of naming an alternative tool or a when-not-to-use-this-instead condition, largely because sibling names are uninformative.

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