Skip to main content
Glama

get_municipality

Read-onlyIdempotent

Fetches Swiss municipality information by name, helping you resolve local administrative data without external API keys.

Instructions

Municipality info by name

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": "get_municipality"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.9.0
    • removedInput schema / properties / name / description
      Removed value: -"Municipality name"
  2. First observed

TDQS

C2.3/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 the safety profile is covered. The description adds nothing beyond that: no note on whether unknown names error or return empty, no indication of matching rules (exact, case-insensitive, partial), and no sense of result size.

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

Conciseness3/5

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

Four words, front-loaded and free of padding, which is structurally clean. However, the brevity is under-specification rather than economy: a slightly longer sentence could have carried the name-format and return-shape information the tool lacks.

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

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, a 0%-described parameter, and no annotation beyond a generic read-only profile, the description must carry the load for a lookup tool – and it does not. An agent cannot know what fields come back or how to format the name input.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% – the single required "name" parameter has no description, type detail, or examples in the schema. The phrase "by name" weakly ties the parameter to a municipality name but leaves the format ambiguous (official German name vs. exonym vs. partial match), so it does not compensate for the coverage gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Municipality info by name" names the resource and the lookup key, but "info" is unspecific about what is actually returned, and nothing distinguishes this from nearby siblings such as search_municipality_energy or geocode. An agent can guess the intent but cannot tell from the text alone why it would pick this over those.

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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives. The agent gets no signal about when this lookup is appropriate versus the municipality-adjacent siblings in the toolset.

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