Skip to main content
Glama
robobobby
by robobobby

no_reverse_geocode

Find Norwegian addresses near geographic coordinates by specifying latitude, longitude, and search radius to locate nearby locations.

Instructions

Find Norwegian addresses near a geographic point (reverse geocoding). Returns addresses within the specified radius.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
latYesLatitude (WGS84, e.g. 59.911 for Oslo)
lonYesLongitude (WGS84, e.g. 10.750 for Oslo)
radiusNoSearch radius in meters (default 100, max 10000)
limitNoMax results (default 10)

Implementation Reference

  • The `no_reverse_geocode` tool implementation using the `apiFetch` helper to call the Kartverket Adresser API.
    server.tool(
      "no_reverse_geocode",
      "Find Norwegian addresses near a geographic point (reverse geocoding). Returns addresses within the specified radius.",
      {
        lat: z.number().describe("Latitude (WGS84, e.g. 59.911 for Oslo)"),
        lon: z.number().describe("Longitude (WGS84, e.g. 10.750 for Oslo)"),
        radius: z.number().min(1).max(10000).optional().describe("Search radius in meters (default 100, max 10000)"),
        limit: z.number().min(1).max(50).optional().describe("Max results (default 10)"),
      },
      async ({ lat, lon, radius, limit }) => {
        try {
          const data = await apiFetch("/punktsok", {
            lat,
            lon,
            radius: radius || 100,
            treffPerSide: limit || 10,
          });
          const total = data.metadata?.totaltAntallTreff || 0;
    
          if (!data.adresser?.length) {
            return { content: [{ type: "text", text: `No addresses found within ${radius || 100}m of ${lat}, ${lon}.` }] };
          }
    
          const lines = [`## Addresses near ${lat.toFixed(4)}°N, ${lon.toFixed(4)}°E (${radius || 100}m radius, ${total} total)\n`];
          for (const a of data.adresser) {
            const dist = a.meterDistanseTilPunkt;
            lines.push(formatAddress(a));
            if (dist != null) lines.push(`Distance: ${Math.round(dist)}m`);
            lines.push("");
          }
          lines.push(`*Kartverket Adresser API*`);
          return { content: [{ type: "text", text: lines.join("\n") }] };
        } 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?

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions the tool returns addresses within a specified radius, but doesn't disclose important traits like whether it's read-only, rate limits, authentication needs, error conditions, or what format the addresses are returned in. 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 extremely concise with just two sentences that efficiently communicate the core purpose and key constraint. Every word earns its place, and the information is front-loaded with the main functionality stated first.

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 tool has no annotations and no output schema, the description is incomplete. It doesn't explain what the return values look like (address format, structure), error conditions, or important behavioral aspects. For a 4-parameter tool with no structured output documentation, the description should provide more context about what to expect from the operation.

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 description mentions 'within the specified radius' which corresponds to the 'radius' parameter, but doesn't add meaningful semantic context beyond what the 100% schema coverage already provides. The schema descriptions fully document each parameter's purpose, constraints, and defaults, so the description adds minimal value here.

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 Norwegian addresses near a geographic point') and resource ('addresses'), distinguishing it from siblings like 'no_address_search' or 'no_postal_code_lookup' by specifying reverse geocoding. It explicitly mentions the geographic scope (Norway) and the operation type (reverse geocoding).

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 context by stating 'Find Norwegian addresses near a geographic point (reverse geocoding)', suggesting it should be used when you have coordinates and need nearby addresses. However, it doesn't explicitly state when NOT to use it or name alternatives like 'dk_reverse_geocode' for Denmark or 'no_address_search' for address-based searches, leaving some ambiguity.

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