Skip to main content
Glama

search_municipality_energy

Read-onlyIdempotent

Find a Swiss municipality's official BFS number by name so you can use it with electricity tariff tools. Enter a place name like Lausanne to get the ID those tools require.

Instructions

Find municipality BFS numbers for the electricity tariff tools

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

Input Schema

NameRequiredDescriptionDefault
nameYese.g. Lausanne

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.9.0
    • changedInput schema / properties / name / description
      Previous value: -"Municipality name to search (e.g. 'Zürich', 'Bern', 'Basel', 'Lausanne', 'Luzern')."New value: +"e.g. Lausanne"
  2. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already establish that this is a safe, read-only, idempotent, open-world lookup. The description adds that the result is a BFS number and that it feeds electricity tariff tools, but it does not disclose matching behavior, ambiguity handling, or return shape for a search operation with no output schema.

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?

The description is a single, front-loaded sentence with no filler. It communicates the resource, output type, and domain of use efficiently.

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?

For a simple one-parameter lookup with strong annotation coverage, the description is mostly complete: it says what is returned and why. It could say more about whether multiple matches are possible or what to do if the name is ambiguous, but the essential context is present.

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 100%, and the single `name` parameter is documented with an example ('e.g. Lausanne'). The description adds no further semantics about exactness, casing, language, or partial matches, so the baseline of 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?

The description states a clear resource—municipality BFS numbers—and ties it to electricity tariff tools, which helps distinguish it from broader sibling tools like get_municipality. It does not use a precise verb such as 'look up by name', but the intended output is still evident.

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?

The phrase 'for the electricity tariff tools' gives a clear usage context: this is a preparatory lookup before calling tariff-related siblings such as get_electricity_tariff or compare_electricity_tariffs. It does not explicitly exclude alternatives like get_municipality or describe when not to use it, so it falls short of full routing guidance.

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