Skip to main content
Glama
reidar80

Norwegian Business Registry MCP Server

by reidar80

get_entity

Retrieve detailed information about Norwegian businesses using their 9-digit organization number. Access company data, board members, subsidiaries, and corporate structure from the official registry.

Instructions

Get detailed information about a specific Norwegian business entity

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
organisasjonsnummerYes9-digit organization number

Implementation Reference

  • MCP CallToolRequest handler case for 'get_entity': extracts organisasjonsnummer from arguments, fetches entity data via apiClient.getEntity, and returns JSON-formatted text content.
    case "get_entity":
      const { organisasjonsnummer } = request.params.arguments as { organisasjonsnummer: string };
      const entity = await apiClient.getEntity(organisasjonsnummer);
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(entity, null, 2),
          },
        ],
      };
  • Input schema for 'get_entity' tool: requires a single 'organisasjonsnummer' string property.
    inputSchema: {
      type: "object",
      properties: {
        organisasjonsnummer: { type: "string", description: "9-digit organization number" }
      },
      required: ["organisasjonsnummer"]
    }
  • Registration of 'get_entity' tool in the ListTools response, including name, description, and input schema.
    {
      name: "get_entity",
      description: "Get detailed information about a specific Norwegian business entity",
      inputSchema: {
        type: "object",
        properties: {
          organisasjonsnummer: { type: "string", description: "9-digit organization number" }
        },
        required: ["organisasjonsnummer"]
      }
    },
  • BrregApiClient helper method that performs the actual API request to fetch entity details by organization number.
    async getEntity(orgNumber: string) {
      return this.makeRequest(`/enhetsregisteret/api/enheter/${orgNumber}`);
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states this is a read operation ('Get'), which is clear, but lacks details on permissions, rate limits, error handling, or response format. For a tool with zero annotation coverage, this is a significant gap in transparency.

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 a single, efficient sentence that front-loads the key information ('Get detailed information about a specific Norwegian business entity'). There is zero waste, making it highly concise and well-structured for quick comprehension.

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 the tool's low complexity (1 parameter, no output schema, no annotations), the description is adequate but incomplete. It clarifies the purpose but misses usage guidelines and behavioral details, making it minimally viable for an agent to attempt use, though with clear gaps in contextual understanding.

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?

The input schema has 100% description coverage, with the parameter 'organisasjonsnummer' documented as a '9-digit organization number'. The description adds no additional parameter semantics beyond this, so it meets the baseline of 3 where the schema does the heavy lifting.

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 verb ('Get') and resource ('detailed information about a specific Norwegian business entity'), making the purpose immediately understandable. However, it doesn't differentiate from siblings like 'get_entity_roles' or 'search_entities' that might also retrieve entity information, so it falls short of a perfect score.

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 no guidance on when to use this tool versus alternatives like 'search_entities' or 'get_entity_roles'. It implies usage for a specific entity but offers no exclusions or context about prerequisites, leaving the agent to guess based on tool names alone.

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/reidar80/BRREG-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server