Skip to main content
Glama

geocode

Convert Swiss addresses or place names to precise coordinates using swisstopo data for location-based applications and mapping.

Instructions

Convert a Swiss address or place name to coordinates (swisstopo)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
addressYesSwiss address or place name

Implementation Reference

  • Handler function for the "geocode" tool (and search_places), which fetches data from the swisstopo API.
    export async function handleGeodata(name: string, args: Record<string, unknown>): Promise<string> {
      switch (name) {
        case "geocode":
        case "search_places": {
          const url = buildUrl(`${BASE}/rest/services/api/SearchServer`, {
            searchText: args.address as string ?? args.query as string,
            type: args.type as string ?? "locations",
            sr: 4326,
            limit: 10,
          });
          const data = await fetchJSON<SearchResponse>(url);
          return JSON.stringify({
            count: data.results.length,
            results: data.results.map(slimSearchResult),
          });
        }
  • Tool definition and input schema for the "geocode" tool.
    export const geodataTools = [
      {
        name: "geocode",
        description: "Convert a Swiss address or place name to coordinates (swisstopo)",
        inputSchema: {
          type: "object",
          required: ["address"],
          properties: {
            address: { type: "string", description: "Swiss address or place name" },
          },
        },
      },
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions the data source ('swisstopo') but lacks details on rate limits, error handling, authentication needs, or output format. For a geocoding tool, this omission is significant as users need to understand reliability and constraints.

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, efficient sentence with zero wasted words. It front-loads the core functionality and includes the data source, making it easy to scan and understand 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 moderate complexity (geocoding with a specific regional focus), no annotations, and no output schema, the description is incomplete. It covers the basic purpose but lacks behavioral details, usage context, and output information, which are crucial for effective tool invocation.

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 schema description coverage is 100%, with the single parameter 'address' well-documented in the schema. The description adds minimal value beyond the schema by specifying 'Swiss address or place name', but doesn't provide additional context like format examples or validation rules. This meets the baseline for high schema coverage.

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: converting Swiss addresses/place names to coordinates using swisstopo. It specifies the verb ('Convert'), resource ('Swiss address or place name'), and target ('coordinates'), distinguishing it from sibling tools like 'reverse_geocode' or 'identify_location'. However, it doesn't explicitly differentiate from 'search_places', which might have overlapping functionality.

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 sibling tools like 'reverse_geocode' (for the inverse operation) or 'search_places' (which might also handle location queries), nor does it specify prerequisites or constraints beyond the Swiss address scope.

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