Skip to main content
Glama

compare_electricity_tariffs

Read-onlyIdempotent

Compare electricity tariffs across 2–20 Swiss municipalities by BFS number to identify cost differences by year and consumption category.

Instructions

Compare electricity tariffs across 2–20 municipalities

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": {
      "municipalities": "<municipalities>"
    },
    "name": "compare_electricity_tariffs"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearNo2011 onward, default: current year
categoryNoH4
municipalitiesYesBFS numbers, e.g. ["261", "351"]

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.9.0
    • addedInput schema / properties / category / default
      Added value: +"H4"
    • removedInput schema / properties / category / description
      Removed value: -"Electricity category (H1–H8, C1–C7). Default: H4."
    • changedInput schema / properties / municipalities / description
      Previous value: -"Array of municipality BFS numbers to compare (e.g. ['261', '351', '6621']). Max 20. Use search_municipality_energy to find IDs."New value: +"BFS numbers, e.g. [\"261\", \"351\"]"
    • changedInput schema / properties / year / description
      Previous value: -"Tariff year (2011–2026). Default: 2026."New value: +"2011 onward, default: current year"
  2. First observed

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is fully covered. Beyond that the description adds nothing: it says nothing about what the comparison returns, how tariffs are ranked or grouped, or how categories affect results.

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 front-loaded clause with no filler or redundancy. It is efficient, though the brevity is partly under-specification rather than disciplined editing.

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

Completeness2/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 is the only place to learn what a "comparison" yields, and it stays silent while leaving the opaque category codes and year semantics unexplained. For a tool whose value depends on interpreting consumption categories, this is a meaningful gap.

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 coverage is 67%, so the schema carries most of the load, including the BFS-number format and the year floor. The description never explains what the category enum (H1–H8, C1–C7) means or how year affects tariffs, so it fails to compensate for the remaining coverage gap; only the 2–20 bound adds anything, and that duplicates minItems/maxItems.

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 ("Compare electricity tariffs") and adds a concrete scope bound (2–20 municipalities), so an agent knows what the tool does. It does not, however, distinguish itself from the sibling get_electricity_tariff, which appears to be 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 Guidelines2/5

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

The only implied usage rule is the 2–20 municipality comparison range, which merely restates the schema constraints. There is no explicit guidance on when to pick this over get_electricity_tariff or search_municipality_energy, and no prerequisites such as needing BFS numbers before calling.

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