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

nordic-registry-mcp-server

by olgasafonova

norway_get_subunit

Read-only

Retrieve details for a Norwegian branch office by its organization number, including name, address, parent org number, and status.

Instructions

Get details for a specific sub-unit (branch office) by its org number. USE WHEN: you have a branch org number and want its details. Returns name, address, parent org number, and status. For listing all branches of a 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": {
      "org_number": "<org_number>"
    },
    "name": "norway_get_subunit"
  }
}

Input Schema

NameRequiredDescriptionDefault
org_numberYes9-digit organization number of the sub-unit (branch office) itself, not of its parent company

Output Schema

NameRequiredDescriptionDefault
sub_unitYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.0.1
    • changedInput schema / properties / org_number / description
      Previous value: -"required"New value: +"9-digit organization number of the sub-unit (branch office) itself, not of its parent company"
  2. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds the returned fields (name, address, parent org number, status), but an output schema exists and captures that, and the idempotentHint=false trait 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 short sentences with zero waste: purpose first, trigger condition second, return contents and routing third. Nothing is repeated or padded.

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

Completeness4/5

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

For a single-parameter read tool with full schema coverage, an output schema, and annotations covering safety, the definition is essentially complete. The only unchecked item is the non-idempotent hint, which is minor here.

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 coverage is 100% and the schema's own property description already says the number is for the sub-unit itself, not the parent, so the description adds no semantics beyond the structured field. Baseline 3 is appropriate.

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?

States a specific verb and resource ('Get details for a specific sub-unit (branch office) by its org number') and immediately disambiguates from the sibling listing tool norway_get_subunits.

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

Usage Guidelines4/5

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

Explicit 'USE WHEN: you have a branch org number and want its details' front-loads the triggering condition, and it names the alternative for the listing case. It does not state exclusions (e.g., use norway_get_company when the number is a parent), so it stops short of a full 5.

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