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

nordic-registry-mcp-server

by olgasafonova

norway_get_company

Read-only

Retrieve Norwegian company details from a 9-digit organization number; spaces and dashes are stripped automatically. Return a compact summary or full record with addresses and industry codes.

Instructions

Get company details by 9-digit org number. USE WHEN: you have an org number and need company details. Spaces and dashes in org number are auto-stripped (e.g., "923 609 016" → "923609016"). Returns compact summary by default; set full=true for complete data including all addresses, industry codes, and capital info. FAILS WHEN: org number is not exactly 9 digits after stripping, or company not found.

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_company"
  }
}

Input Schema

NameRequiredDescriptionDefault
fullNoReturn the full company record (all addresses, industry codes, capital) instead of the compact summary (default false)
org_numberYes9-digit Norwegian organization number; spaces and dashes are stripped automatically, e.g. 923609016 or 923 609 016

Output Schema

NameRequiredDescriptionDefault
foundYes
companyNo
messageNo
summaryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv2.0.1
    • addedInput schema / properties / full / description
      Added value: +"Return the full company record (all addresses, industry codes, capital) instead of the compact summary (default false)"
    • changedInput schema / properties / org_number / description
      Previous value: -"required"New value: +"9-digit Norwegian organization number; spaces and dashes are stripped automatically, e.g. 923609016 or 923 609 016"
    • addedInput schema / properties / org_number / x-mcp-header
      Added value: +"Org-Number"
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the annotations, the description discloses auto-stripping of spaces and dashes, the compact-by-default return shape, how full=true changes the response, and explicit failure conditions. This adds substantial behavioral context for an agent.

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 compact, front-loaded, and organized into clear USE WHEN and FAILS WHEN sections. Every sentence provides actionable information with no filler.

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?

Given that an output schema exists, the description need not explain return values. It covers input normalization, default versus full mode, and failure conditions, making it complete for this lookup tool.

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%, so both parameters are already documented in the input schema. The description reinforces org number normalization with an example and explains full=true, but adds little beyond structured parameter descriptions.

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 uses a specific verb and resource: get company details by 9-digit organization number. It clearly distinguishes this from search-based siblings by requiring an org number as the lookup key.

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?

The 'USE WHEN' line gives a clear condition: when you have an org number and need company details. It does not explicitly name alternatives such as norway_search_companies for when no org number is available, but the usage context is still clear.

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