Skip to main content
Glama
robobobby
by robobobby

dk_reverse_geocode

Convert latitude/longitude coordinates to the nearest Danish address with full details for location-based applications and data analysis.

Instructions

Find the nearest Danish address to a given latitude/longitude coordinate. Returns the closest address with full details.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
latitudeYesLatitude (WGS84), e.g. 55.676
longitudeYesLongitude (WGS84), e.g. 12.568

Implementation Reference

  • The implementation of the `dk_reverse_geocode` tool, which uses the DAWA API to find the nearest address for given coordinates.
    server.tool(
      "dk_reverse_geocode",
      "Find the nearest Danish address to a given latitude/longitude coordinate. Returns the closest address with full details.",
      {
        latitude: z.number().min(54).max(58).describe("Latitude (WGS84), e.g. 55.676"),
        longitude: z.number().min(7).max(16).describe("Longitude (WGS84), e.g. 12.568"),
      },
      async ({ latitude, longitude }) => {
        try {
          const data = await dawaFetch("/adgangsadresser/reverse", {
            x: longitude,
            y: latitude,
            struktur: "mini",
          });
          return { content: [{ type: "text", text: formatAddress(data) }] };
        } catch (err) {
          return { content: [{ type: "text", text: `Error: ${err.message}` }], isError: true };
        }
      }
    );
Behavior2/5

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

No annotations are provided, so the description carries full burden. It mentions returning 'the closest address with full details,' which gives some behavioral insight, but does not disclose potential limitations (e.g., accuracy, rate limits, authentication needs, error handling, or what 'full details' entails). 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 two concise sentences with zero waste: the first states the purpose and input, the second clarifies the output. It is front-loaded with the core functionality and efficiently structured.

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 no annotations and no output schema, the description is moderately complete for a simple lookup tool. It covers the basic purpose and output intent ('full details'), but lacks details on return format, error cases, or operational constraints. For a tool with 2 parameters and 100% schema coverage, it meets minimum viability but could be more informative.

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

Parameters4/5

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

Schema description coverage is 100%, so the schema already documents both parameters thoroughly with descriptions and numeric ranges. The description adds minimal value by specifying 'latitude/longitude coordinate' but does not provide additional semantics beyond what the schema offers. With 0 parameters needing extra explanation, a baseline of 4 is appropriate as it slightly reinforces the purpose.

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 specific action ('Find the nearest Danish address') with the resource ('given latitude/longitude coordinate') and distinguishes it from siblings like 'dk_address_search' and 'dk_nearby_addresses' by specifying reverse geocoding to a single nearest address rather than searching or listing multiple addresses.

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 description implies usage for converting coordinates to addresses in Denmark, but does not explicitly state when to use this tool versus alternatives like 'dk_nearby_addresses' (which might return multiple addresses) or 'no_reverse_geocode' (for Norway). It provides basic context but lacks explicit exclusions or comparisons.

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/robobobby/mcp-nordic'

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