Skip to main content
Glama

Electricity tariff for a municipality

get_electricity_tariff
Read-only

Retrieve official ElCom electricity tariffs for a Swiss municipality, broken down by energy, grid, community charges and federal surcharge for household or commercial consumption categories.

Instructions

Official ElCom electricity tariff for a Swiss municipality, broken into energy, grid usage, community charges and federal grid surcharge (Rp./kWh). Categories: H1–H8 households (H4 = typical 4-room flat), C1–C7 commercial.

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": {
      "municipality": "<municipality>"
    },
    "name": "get_electricity_tariff"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearNoTariff year (default: current year)
categoryNoConsumption category (default H4)H4
municipalityYesMunicipality name (e.g. 'Baden') or BFS number

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds genuinely useful context beyond them: the data is official ElCom data, values are denominated in Rp./kWh, and the result is split into four named cost components, which tells the agent what it will receive and how to interpret it.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences with no filler: the first establishes source, scope, output composition and unit; the second disambiguates the category codes. The most decision-relevant information (what it returns and in what unit) is front-loaded.

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, the description carries the burden of describing the return value, and it does so adequately by naming the four tariff components and their unit. Minor gaps remain (no mention of failure behavior for unresolvable municipality names or years without published tariffs), but nothing essential for a correct call is missing.

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 coverage is 100%, so baseline is 3. The description earns above baseline by explaining the enum semantics the schema only lists: H1–H8 are households, H4 corresponds to a typical 4-room flat (the default), and C1–C7 are commercial categories, which meaningfully guides category selection.

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 resource (official ElCom electricity tariff) with its authoritative source, scope (a single Swiss municipality) and return breakdown (energy, grid usage, community charges, federal grid surcharge in Rp./kWh). It does not name or contrast with the obvious sibling compare_electricity_tariffs, so an agent must infer that this is the single-municipality lookup.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: the phrase 'for a Swiss municipality' signals a single-location lookup rather than a comparison, which tacitly separates it from compare_electricity_tariffs. There is no explicit when-to-use/when-not-to-use guidance or note about what happens if the municipality is unknown or the year is out of range.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools