Skip to main content
Glama

Compare electricity tariffs across municipalities

compare_electricity_tariffs
Read-only

Compare official total electricity tariffs (Rp./kWh) across up to 10 Swiss municipalities for one category and year, reporting unresolved names or missing tariffs per item.

Instructions

Compare official electricity tariffs (total Rp./kWh, standard product) across up to 10 Swiss municipalities for one category and year. Names that can't be resolved or have no tariff are reported per item in errors without failing the comparison.

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
yearNo
categoryNoH4
municipalitiesYesMunicipality names or BFS numbers, e.g. ['Zürich','Baden','Bern']

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 and openWorldHint, so the safety profile is covered; the description adds real value beyond that by disclosing partial-failure semantics — unresolvable names or missing tariffs are returned per item in `errors` rather than aborting the call. It does not cover what happens when the optional year is omitted or any rate/limit behavior.

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 sentences, zero filler: the scope and units come first, and the error-handling clause follows. Nothing is repeated from the schema verbatim and no sentence could be dropped without losing information.

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?

There is no output schema, so the description carries the burden of describing the return, and it only covers the `errors` portion — the shape of the successful comparison result (per-municipality values, ordering) is unstated. It also omits what happens when the optional year is not supplied, which matters because the schema defines no default for it.

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?

With schema coverage at 33%, the description partially compensates: it confirms municipalities are names (or BFS numbers, per the schema), caps the set at 10, and frames year/category as single-value selections. However, it never explains what the H1–H8/C1–C7 category codes mean or how the default H4 is applied, leaving the largest semantic gap in the schema unaddressed.

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?

States a specific verb (Compare) and resource (official electricity tariffs, total Rp./kWh, standard product) with explicit scope: up to 10 Swiss municipalities, one category and year. That scope alone separates it from a single-municipality tariff lookup among the siblings.

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 implied by the scope ('across up to 10 Swiss municipalities for one category and year'), so an agent can infer this is the multi-municipality comparison tool. There is no explicit when-to-use versus when-not guidance, and no pointer to the single-tariff sibling for one-off lookups.

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