Skip to main content
Glama

reverse_geocode

Convert geographic coordinates into Swiss addresses using swisstopo data. Provide latitude and longitude to retrieve location information.

Instructions

Convert coordinates to a Swiss address (swisstopo)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
latYesLatitude (WGS84)
lngYesLongitude (WGS84)

Implementation Reference

  • The handler implementation for the 'reverse_geocode' tool, which fetches data from the swisstopo SearchServer.
    case "reverse_geocode": {
      const lat = args.lat as number;
      const lng = args.lng as number;
      const url = buildUrl(`${BASE}/rest/services/api/SearchServer`, {
        searchText: `${lat},${lng}`,
        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 input schema definition for the 'reverse_geocode' tool.
    {
      name: "reverse_geocode",
      description: "Convert coordinates to a Swiss address (swisstopo)",
      inputSchema: {
        type: "object",
        required: ["lat", "lng"],
        properties: {
          lat: { type: "number", description: "Latitude (WGS84)" },
          lng: { type: "number", description: "Longitude (WGS84)" },
        },
      },
    },
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. It mentions the data source ('swisstopo') but does not disclose behavioral traits such as rate limits, error handling, response format, or whether it's a read-only operation. The description is minimal and lacks critical operational context.

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

Conciseness4/5

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

The description is a single, efficient sentence that directly states the tool's purpose without unnecessary words. It is front-loaded with the core function, though it could be slightly more structured by including usage context. No waste, but minimal.

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

Completeness2/5

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

Given the lack of annotations and output schema, the description is incomplete. It does not explain what the output looks like (e.g., address format), error conditions, or limitations (e.g., only works for Swiss coordinates). For a tool with no structured output documentation, this leaves significant gaps for an AI agent.

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 both parameters ('lat' and 'lng') well-documented in the schema. The description adds no additional parameter semantics beyond what the schema provides, such as coordinate ranges or precision. Baseline 3 is appropriate when the schema does the heavy lifting.

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?

The description clearly states the tool's purpose with a specific verb ('Convert') and resource ('coordinates to a Swiss address'), and it distinguishes itself from sibling tools by specifying the geographic scope ('Swiss') and data source ('swisstopo'). This is more specific than the generic 'geocode' sibling tool.

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 does not mention the sibling 'geocode' tool or specify that this is for Swiss addresses only, which might be implied but not explicitly stated. No prerequisites or exclusions are provided.

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