Skip to main content
Glama

get_municipality

Retrieve detailed information about Swiss municipalities by name, including location data and administrative details, using open Swiss geodata.

Instructions

Get information about a Swiss municipality by name

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesMunicipality name

Implementation Reference

  • The handler implementation for get_municipality which fetches municipality data from the SearchServer API.
    case "get_municipality": {
      const url = buildUrl(`${BASE}/rest/services/api/SearchServer`, {
        searchText: args.name as string,
        type: "locations",
        sr: 4326,
        limit: 5,
      });
      const data = await fetchJSON<SearchResponse>(url);
      return JSON.stringify({
        count: data.results.length,
        results: data.results.map(slimSearchResult),
      });
    }
  • The tool definition/schema for get_municipality.
      name: "get_municipality",
      description: "Get information about a Swiss municipality by name",
      inputSchema: {
        type: "object",
        required: ["name"],
        properties: {
          name: { type: "string", description: "Municipality name" },
        },
      },
    },
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool 'Get[s] information,' implying a read-only operation, but doesn't specify what type of information is returned (e.g., demographic data, location details), whether there are rate limits, authentication needs, or error handling. For a tool with no annotations, this leaves significant gaps in understanding its 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?

The description is a single, clear sentence with no wasted words: 'Get information about a Swiss municipality by name.' It is front-loaded and efficiently communicates the core purpose without unnecessary elaboration, making it easy for an agent to parse quickly.

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?

Given the tool's simplicity (one parameter, 100% schema coverage, no output schema), the description is adequate but incomplete. It lacks details on the information returned, potential errors, or usage context, which are important for an agent to invoke it correctly. Without annotations or an output schema, the description should do more to compensate, but it meets a minimal viable standard.

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?

The input schema has 100% description coverage, with the single parameter 'name' documented as 'Municipality name.' The description adds minimal value beyond this, only reinforcing that input is 'by name.' Since the schema already fully describes the parameter, the baseline score of 3 is appropriate, as the description doesn't provide additional syntax, format details, or examples.

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 clearly states the tool's purpose: 'Get information about a Swiss municipality by name.' It specifies the verb ('Get'), resource ('Swiss municipality'), and key input ('by name'), making it easy to understand what the tool does. However, it doesn't explicitly differentiate from sibling tools like 'search_municipality_energy' or 'list_cantons,' which slightly limits its clarity in a crowded toolset.

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 description provides no guidance on when to use this tool versus alternatives. It doesn't mention any prerequisites, exclusions, or comparisons to sibling tools such as 'geocode,' 'identify_location,' or 'search_places,' which might offer overlapping functionality. This lack of context leaves the agent to infer usage based on the tool name alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/vikramgorla/mcp-swiss'

If you have feedback or need assistance with the MCP directory API, please join our Discord server