Skip to main content
Glama

get_electricity_tariff

Read-onlyIdempotent

Retrieve ElCom electricity tariffs (Rp./kWh) and component breakdown for a Swiss municipality by BFS number, with optional year and consumption category filters.

Instructions

ElCom electricity tariff (Rp./kWh) for a municipality, with component breakdown

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
yearNo2011 onward, default: current year
categoryNoH1–H8 household (H4 ≈ 4500 kWh/yr), C1–C7 commercialH4
municipalityYesBFS number, e.g. 261 (Zürich), 351 (Bern); see search_municipality_energy

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.9.0
    • addedInput schema / properties / category / default
      Added value: +"H4"
    • changedInput schema / properties / category / description
      Previous value: -"Electricity category. Household: H1–H8 (H4 is default, ~4500 kWh/year). Commercial: C1–C7. Default: H4."New value: +"H1–H8 household (H4 ≈ 4500 kWh/yr), C1–C7 commercial"
    • changedInput schema / properties / municipality / description
      Previous value: -"Municipality BFS number (e.g. '261' for Zürich, '351' for Bern, '6621' for Genève). Use search_municipality_energy to find the ID."New value: +"BFS number, e.g. 261 (Zürich), 351 (Bern); see search_municipality_energy"
    • changedInput schema / properties / year / description
      Previous value: -"Tariff year (2011–2026). Default: current year (2026)."New value: +"2011 onward, default: current year"
  2. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so safety is covered. The description adds that the result includes a component breakdown and is denominated in Rp./kWh, but says nothing about default year behaviour, category fallbacks, or what happens when data is missing for a municipality/year.

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?

A single short sentence with the resource, unit and scope front-loaded, and no filler. It is arguably too terse rather than padded, but every word earns its place.

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?

With no output schema, the description must carry return-shape information; 'with component breakdown' is a useful but thin hint about what fields come back. For a simple three-parameter read tool with fully documented parameters this is adequate, though an agent still cannot anticipate the response structure or empty-result behaviour.

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%, with the year range, the H1–H8/C1–C7 enum semantics and BFS number examples all documented in the schema. The description adds only the unit of the returned value, which is a return-value detail rather than parameter meaning; baseline 3 is appropriate.

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 (ElCom electricity tariff), its unit (Rp./kWh), the scope (a municipality) and that a component breakdown is returned. It implicitly distinguishes itself from the sibling compare_electricity_tariffs by being a single-municipality lookup, but never names that sibling explicitly.

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: 'for a municipality' suggests a single-location lookup rather than a comparison, and the schema's municipality field points to search_municipality_energy for BFS numbers. The description itself offers no explicit when-to-use/when-not guidance or alternative tool routing.

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