Skip to main content
Glama
robobobby
by robobobby

no_municipality_addresses

Find addresses in Norwegian municipalities by specifying a location and optional street filter. Retrieve structured address data for planning, verification, or analysis purposes.

Instructions

List addresses in a Norwegian municipality. Can filter by street name.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
municipalityYesMunicipality name (e.g. 'OSLO', 'BERGEN', 'TRONDHEIM', 'STAVANGER', 'TROMSØ')
streetNoOptional street name filter
limitNoMax results (default 10)

Implementation Reference

  • The "no_municipality_addresses" tool definition and its handler implementation, which queries the Kartverket Adresser API.
    server.tool(
      "no_municipality_addresses",
      "List addresses in a Norwegian municipality. Can filter by street name.",
      {
        municipality: z.string().describe("Municipality name (e.g. 'OSLO', 'BERGEN', 'TRONDHEIM', 'STAVANGER', 'TROMSØ')"),
        street: z.string().optional().describe("Optional street name filter"),
        limit: z.number().min(1).max(50).optional().describe("Max results (default 10)"),
      },
      async ({ municipality, street, limit }) => {
        try {
          const params = {
            kommunenavn: municipality,
            treffPerSide: limit || 10,
          };
          if (street) params.adressenavn = street;
    
          const data = await apiFetch("/sok", params);
          const total = data.metadata?.totaltAntallTreff || 0;
    
          if (!data.adresser?.length) {
            return { content: [{ type: "text", text: `No addresses found in municipality "${municipality}".` }] };
          }
    
          const lines = [`## Addresses in ${municipality} (${total} total)\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?

No annotations are provided, so the description carries full burden. It states it's a listing tool with filtering, implying read-only behavior, but doesn't disclose pagination, rate limits, authentication needs, error conditions, or output format. For a tool with no annotations, this leaves significant behavioral gaps.

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—two short sentences with zero wasted words. It's front-loaded with the core purpose and efficiently adds the filtering capability. Every sentence earns its place.

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 incomplete for a tool that returns address data. It covers the basic purpose and one parameter aspect but lacks details on output structure, error handling, or behavioral constraints. It's minimally adequate but has clear gaps.

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 parameters are well-documented in the schema. The description adds minimal value beyond the schema by mentioning the street filter, but doesn't provide additional context like format examples or usage tips. Baseline 3 is appropriate given 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: 'List addresses in a Norwegian municipality' specifies the verb (list) and resource (addresses), with geographic scope (Norwegian municipality). It distinguishes from some siblings like 'no_address_search' by focusing on municipality-based listing rather than general search, though not all sibling distinctions are explicit.

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 minimal guidance: it mentions filtering by street name but doesn't explain when to use this tool versus alternatives like 'no_address_search' or 'no_postal_code_lookup'. No context on prerequisites, typical use cases, or exclusions is provided.

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