Skip to main content
Glama

Get municipality at coordinates

get_municipality
Read-only

Find the Swiss municipality containing a WGS84 coordinate and return its official BFS number and canton. Use it to resolve GPS points to communes for geospatial and administrative lookups.

Instructions

Return the Swiss municipality (Gemeinde) containing the given WGS84 point, including its official BFS number and canton.

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": {
      "lat": "<lat>",
      "lon": "<lon>"
    },
    "name": "get_municipality"
  }
}

Input Schema

NameRequiredDescriptionDefault
latYesWGS84 latitude (Switzerland: ~45.8–47.9)
lonYesWGS84 longitude (Switzerland: ~5.9–10.6)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A3.6/5.0
Behavior3/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 that the response carries the BFS number and canton. It does not disclose what happens for out-of-Switzerland coordinates, despite the schema clamping lat/lon to a Swiss bounding box — a meaningful behavioral gap for a lookup tool.

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?

A single sentence that front-loads the verb and resource and then names the returned fields. No filler, no repetition of schema ranges.

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 two-parameter, non-destructive point lookup with no output schema, the description covers the core output fields (BFS number, canton) so an agent knows what it gets back. The only notable omission is error/empty behavior for points outside Switzerland, which is minor against the full schema coverage and annotations.

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 description coverage is 100%, with each parameter already documenting WGS84 meaning and expected Swiss ranges, so the baseline is 3. The description only echoes "WGS84 point" and adds no coordinate-order, precision, or edge-case semantics beyond the schema.

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 ("Return the Swiss municipality (Gemeinde) containing the given WGS84 point") and names the payload (official BFS number and canton). The point-in-polygon framing implicitly separates it from name/BFS-keyed siblings such as get_swiss_municipality_facts, but no sibling is named explicitly.

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?

The phrase "containing the given WGS84 point" implies this is the coordinate-to-municipality lookup, which is usable guidance. There is no explicit when-to-use, no named alternative for reverse lookups, and no stated condition for points outside Switzerland or in border/water areas.

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