Skip to main content
Glama

Registry Pages

Norwegian company by organisation number

get_norwegian_company
Read-only

Central Coordinating Register for Legal Entities (Brønnøysund) data for one Norwegian unit: name, legal form, status, founding date, business address, industry, employees, VAT registration, and the page URL to cite.

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": {
      "orgnr": "<orgnr>"
    },
    "name": "get_norwegian_company"
  }
}

Input Schema

NameRequiredDescriptionDefault
orgnrYes9-digit organisation number, for example 923609016

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered; the description still adds real value by naming the authoritative registry and enumerating the returned attributes, including a page URL 'to cite'. It does not state behavior for unknown or deregistered organisation numbers, which keeps it short of a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One dense sentence with no filler, and the field list is compact. It leads with the registry name rather than the operation, which slightly delays the most decision-relevant information, but nothing is wasted.

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?

With no output schema, enumerating the returned fields (name, legal form, status, address, industry, employees, VAT, citation URL) is exactly what the description needs to supply, and it does so. The main remaining gap is error/empty-result behavior for an invalid or unregistered number, minor for a one-parameter read 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 description coverage is 100% and the single parameter 'orgnr' is documented with a 9-digit format and an example, so the schema carries the burden. The description adds no format or validation detail beyond saying 'one Norwegian unit', matching the baseline for fully-covered params.

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 names the specific source registry (Brønnøysund / Central Coordinating Register for Legal Entities) and the resource ('one Norwegian unit'), and enumerates the data returned. Combined with the title, an agent can tell this is a single-entity lookup distinct from the search_* siblings, though the retrieval verb itself is only implied.

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

Usage Guidelines3/5

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

The phrase 'for one Norwegian unit' implies a single-entity lookup keyed by identifier, which indirectly separates it from search_norwegian_companies, but there is no explicit when-to-use or when-not-to-use statement. No guidance on what to do when the organisation number is unknown — the search sibling is never named.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources