Skip to main content
Glama
robobobby
by robobobby

dk_nearby_addresses

Find addresses within a specified radius of coordinates in Denmark to explore areas or discover nearby locations.

Instructions

Find addresses within a radius of a coordinate. Useful for exploring an area or finding what's around a location.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
latitudeYesCenter latitude
longitudeYesCenter longitude
radius_metersNoSearch radius in meters (default 200, max 5000)
limitNoMax results (default 10)

Implementation Reference

  • Handler logic for dk_nearby_addresses, which fetches data from the DAWA API and formats the result.
      async ({ latitude, longitude, radius_meters, limit }) => {
        try {
          const data = await dawaFetch("/adgangsadresser", {
            cirkel: `${longitude},${latitude},${radius_meters || 200}`,
            struktur: "mini",
            per_side: limit || 10,
          });
          if (!data.length) return { content: [{ type: "text", text: "No addresses found within radius." }] };
          const lines = data.map((a, i) => {
            const dist = haversine(latitude, longitude, a.y, a.x);
            return `${i + 1}. **${a.betegnelse}** (${dist}m away)\n   ${a.y.toFixed(6)}°N, ${a.x.toFixed(6)}°E`;
          });
          return { content: [{ type: "text", text: `## Addresses within ${radius_meters || 200}m\n\n${lines.join("\n")}` }] };
        } catch (err) {
          return { content: [{ type: "text", text: `Error: ${err.message}` }], isError: true };
        }
      }
    );
  • Registration of the dk_nearby_addresses tool with its schema definition using Zod.
    server.tool(
      "dk_nearby_addresses",
      "Find addresses within a radius of a coordinate. Useful for exploring an area or finding what's around a location.",
      {
        latitude: z.number().min(54).max(58).describe("Center latitude"),
        longitude: z.number().min(7).max(16).describe("Center longitude"),
        radius_meters: z.number().min(1).max(5000).optional().describe("Search radius in meters (default 200, max 5000)"),
        limit: z.number().min(1).max(50).optional().describe("Max results (default 10)"),
      },
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 mentions the tool is for 'exploring an area or finding what's around a location,' which implies a read-only, non-destructive operation, but it doesn't specify details like rate limits, authentication needs, error handling, or what the output looks like (e.g., format, pagination). 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 concise and well-structured, consisting of two sentences: one stating the purpose and another providing usage context. Every sentence earns its place without redundancy, making it easy to scan and understand quickly. It's appropriately sized for the tool's complexity.

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 has no annotations and no output schema, the description is somewhat incomplete. It covers the basic purpose and usage but lacks details on behavioral traits (e.g., performance, errors) and output format. However, the input schema is well-documented, and the description provides adequate context for a simple query tool, though it could benefit from more completeness given the absence of structured fields.

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 clear parameter descriptions (e.g., 'Center latitude', 'Search radius in meters'). The description adds minimal value beyond the schema by implying the tool uses a coordinate and radius, but it doesn't provide additional semantics like units clarification or usage examples. Given the high schema coverage, a baseline score of 3 is appropriate as the schema does most of the work.

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: 'Find addresses within a radius of a coordinate.' It specifies the verb ('Find'), resource ('addresses'), and scope ('within a radius of a coordinate'), making it easy to understand. However, it doesn't explicitly differentiate from sibling tools like 'dk_address_search' or 'dk_reverse_geocode', which might have overlapping functionality, so it doesn't reach a score of 5.

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 provides implied usage guidance by stating it's 'Useful for exploring an area or finding what's around a location.' This gives context for when to use the tool, but it doesn't explicitly mention when not to use it or name alternatives among the many sibling tools. For example, it doesn't clarify if this is better than 'dk_address_search' for radius-based queries, so it's not fully explicit.

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