Skip to main content
Glama
nordic-registry-mcp-server

nordic-registry-mcp-server

by olgasafonova

norway_search_subunits

Read-only

Search Norwegian branch offices by name when you lack the parent org number. Filter results by municipality code and get partial, case-insensitive matches.

Instructions

Search Norwegian branch offices by name. USE WHEN: "find branches named X" and you don't have the parent org number. Partial matches and case-insensitive. Filter by municipality (4-digit code, use norway_list_municipalities to look up codes). For listing all branches of a known parent, use norway_get_subunits.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "norway_search_subunits"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, 0-indexed (default 0)
sizeNoResults per page, 1-100 (default 20); values above 100 are rejected
queryYesSub-unit (branch office) name to search for; partial and case-insensitive matches, 2-500 characters
municipalityNo4-digit Norwegian municipality code to filter by, e.g. 0301 for Oslo. Use norway_list_municipalities to look up codes

Output Schema

NameRequiredDescriptionDefault
pageYes
sub_unitsYes
total_pagesYes
total_resultsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv2.0.1
    • addedInput schema / properties / municipality / description
      Added value: +"4-digit Norwegian municipality code to filter by, e.g. 0301 for Oslo. Use norway_list_municipalities to look up codes"
    • addedInput schema / properties / page / description
      Added value: +"Page number, 0-indexed (default 0)"
    • changedInput schema / properties / query / description
      Previous value: -"required"New value: +"Sub-unit (branch office) name to search for; partial and case-insensitive matches, 2-500 characters"
    • addedInput schema / properties / size / description
      Added value: +"Results per page, 1-100 (default 20); values above 100 are rejected"
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint and idempotentHint, so the safety profile is covered; the description adds matching semantics (partial, case-insensitive) and the municipality filtering constraint. It stops short of describing result ordering, empty-result behavior, or paging limits beyond what the schema states, and the idempotentHint=false is left unexplained.

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?

Three compact sentences, all front-loaded: purpose first, then the usage trigger, then the exclusion and code-lookup pointer. No filler or restated title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a four-parameter read-only search with a full output schema and annotations covering safety, the description supplies everything needed to choose and call it correctly, including the cross-tool dependency for municipality codes.

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 query, municipality, page, and size are already fully documented with examples and bounds. The description restates the query matching semantics and the municipality code lookup but adds no format or behavior detail the schema lacks, so the baseline 3 applies.

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 opens with a specific verb and resource ('Search Norwegian branch offices by name') and implicitly restricts scope to branches whose parent org number is unknown, which separates it from norway_get_subunits and norway_search_companies.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives an explicit USE WHEN trigger ('find branches named X' without the parent org number) and names the alternative for the opposite case ('For listing all branches of a known parent, use norway_get_subunits'), plus routes municipality code lookup to norway_list_municipalities.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.