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

ElCom-Tarif 2027 (H4) und PVGIS-Ertrag für eine Schweizer PLZ

ch_elcom_tariff_lookup

Read-onlyIdempotent

[Markt: CH | Norm: StromVV / ElCom-Tarife 2027, Kategorie H4 (4 500 kWh/a); JRC PVGIS v5.3] Liefert für eine Schweizer Postleitzahl die H4-Strompreiskomponenten (Energie, Netz, Abgaben, Messung) in Rp./kWh netto, den Gesamtpreis, den PVGIS-Jahresertrag in kWh/kWp, die Höhe in m ü. M. und die Auslegungs-Tiefsttemperatur. WANN VERWENDEN: Wenn für eine PV- oder Eigenverbrauchsrechnung in der Schweiz der örtliche Tarif und Standortertrag benötigt wird. EINGABEN: plz = Schweizer Postleitzahl (1000–9658). GRENZEN: Unverbindliche Vorbemessung (Netzgebiets-Mittel je PLZ, kein individueller Tarif eines Anschlusses; keine Mehrwertsteuer; keine Rückliefertarife).

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>"
    },
    "name": "ch_elcom_tariff_lookup"
  }
}

Input Schema

Name	Required	Description	Default
`plz`	Yes	4 Ziffern, 1000–9658

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 7, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations already mark it read-only, idempotent and closed-world; the description adds genuine behavioral context beyond that: values are net (excl. VAT), tariffs are network-area means per PLZ rather than an individual connection tariff, feed-in tariffs are out of scope, and results are non-binding preliminary sizing. It also documents the data sources and vintage, which matters for trusting the numbers.

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?

One dense paragraph with bracketed section markers (market/norm, when-to-use, inputs, limits) that front-loads the purpose and then the constraints. Every clause carries information, though the header bracket partly duplicates the title.

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

Completeness5/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 must describe the return values, and it lists every returned field plus units. For a one-parameter read-only lookup it covers sources, scope limits and output content completely.

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?

There is a single parameter with 100% schema description coverage, and the description's 'EINGABEN' line only restates the range 1000–9658 already given in the schema. Baseline 3 applies since the schema carries the full burden and the description adds no format or edge-case detail.

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 description names the exact outputs (H4 tariff components in Rp./kWh, total price, PVGIS annual yield in kWh/kWp, altitude, design low temperature) for a specific resource (a Swiss postal code) under named standards (StromVV/ElCom 2027, PVGIS v5.3). This is far more specific than the opaque bot_* sibling names and leaves no ambiguity about what the tool returns.

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' clause states the use case (PV or self-consumption calculation in Switzerland) and the 'GRENZEN' clause states what the tool is not (binding individual tariffs, VAT, feed-in tariffs). It does not name an alternative tool for those excluded cases, 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.

All https://fachrechner.com/api/v1/mcp tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?