Skip to main content
Glama
robobobby
by robobobby

no_address_search

Search Norwegian addresses using text queries, with filters for postal codes and municipalities. Find locations by street names, full addresses, or postal codes.

Instructions

Search for Norwegian addresses by text query. Supports street names, full addresses, postal codes, and municipality filtering.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesAddress search query (e.g. 'Karl Johans gate 1', 'Storgata Oslo', 'Bryggen Bergen')
postal_codeNoFilter by postal code (4 digits, e.g. '0154')
municipalityNoFilter by municipality name (e.g. 'OSLO', 'BERGEN', 'TRONDHEIM')
limitNoMax results (default 10, max 50)
fuzzyNoEnable fuzzy matching for misspellings (default false)

Implementation Reference

  • The 'no_address_search' tool is registered and its handler is defined here using the Kartverket Adresser API to search for Norwegian addresses based on a query and optional filters.
    server.tool(
      "no_address_search",
      "Search for Norwegian addresses by text query. Supports street names, full addresses, postal codes, and municipality filtering.",
      {
        query: z.string().describe("Address search query (e.g. 'Karl Johans gate 1', 'Storgata Oslo', 'Bryggen Bergen')"),
        postal_code: z.string().optional().describe("Filter by postal code (4 digits, e.g. '0154')"),
        municipality: z.string().optional().describe("Filter by municipality name (e.g. 'OSLO', 'BERGEN', 'TRONDHEIM')"),
        limit: z.number().min(1).max(50).optional().describe("Max results (default 10, max 50)"),
        fuzzy: z.boolean().optional().describe("Enable fuzzy matching for misspellings (default false)"),
      },
      async ({ query, postal_code, municipality, limit, fuzzy }) => {
        try {
          const params = {
            sok: query,
            treffPerSide: limit || 10,
          };
          if (postal_code) params.postnummer = postal_code;
          if (municipality) params.kommunenavn = municipality;
          if (fuzzy) params.fuzzy = "true";
    
          const data = await apiFetch("/sok", params);
          const total = data.metadata?.totaltAntallTreff || 0;
    
          if (!data.adresser?.length) {
            return { content: [{ type: "text", text: `No addresses found for "${query}".` }] };
          }
    
          const lines = [`## Address Search: "${query}" (${total} total results)\n`];
          for (const a of data.adresser) {
            lines.push(formatAddress(a));
            lines.push("");
          }
          lines.push(`*Kartverket Adresser API — showing ${data.adresser.length} of ${total}*`);
          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 full burden for behavioral disclosure. It mentions what types of queries are supported (street names, full addresses, postal codes, municipality filtering) but doesn't describe response format, error conditions, rate limits, authentication needs, or whether this is a read-only operation. For a search tool with 5 parameters, this is insufficient.

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 perfectly concise - a single sentence that efficiently communicates the core functionality. Every word earns its place, with no redundant information or unnecessary elaboration.

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?

For a search tool with 5 parameters, no annotations, and no output schema, the description is incomplete. It doesn't explain what the tool returns (address objects? coordinates? partial matches?), error handling, or performance characteristics. The agent would need to guess about the response format and behavior.

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%, so the schema already documents all parameters thoroughly. The description adds marginal value by listing the supported query types (street names, full addresses, postal codes, municipality filtering), which helps contextualize the 'query' parameter but doesn't provide additional semantics beyond what's in the schema descriptions.

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: 'Search for Norwegian addresses by text query.' It specifies the resource (Norwegian addresses) and verb (search), but doesn't explicitly differentiate from sibling tools like 'no_municipality_addresses' or 'no_postal_code_lookup' that might overlap in 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. With multiple Norwegian address-related tools in the sibling list (no_municipality_addresses, no_postal_code_lookup, no_reverse_geocode), there's no indication of which scenarios favor this general search tool over more specific ones.

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