Skip to main content
Glama
reidar80

Norwegian Business Registry MCP Server

by reidar80

get_sub_entity

Retrieve detailed information about specific Norwegian business sub-entities using their 9-digit organization number to access corporate structure and governance data.

Instructions

Get detailed information about a specific Norwegian business sub-entity

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
organisasjonsnummerYes9-digit organization number

Implementation Reference

  • Core handler function in BrregApiClient class that makes the HTTP request to the BRREG API to fetch detailed information about a specific sub-entity (underenhet) by its organization number.
    async getSubEntity(orgNumber: string) {
      return this.makeRequest(`/enhetsregisteret/api/underenheter/${orgNumber}`);
    }
  • JSON schema defining the input parameters for the get_sub_entity tool: requires a 9-digit organisasjonsnummer string.
    inputSchema: {
      type: "object",
      properties: {
        organisasjonsnummer: { type: "string", description: "9-digit organization number" }
      },
      required: ["organisasjonsnummer"]
    }
  • Tool registration in the ListTools response, including name, description, and input schema.
    {
      name: "get_sub_entity",
      description: "Get detailed information about a specific Norwegian business sub-entity",
      inputSchema: {
        type: "object",
        properties: {
          organisasjonsnummer: { type: "string", description: "9-digit organization number" }
        },
        required: ["organisasjonsnummer"]
      }
    },
  • MCP server handler case that extracts the organization number from tool arguments, calls the apiClient handler, and returns the JSON-formatted response as text content.
    case "get_sub_entity":
      const { organisasjonsnummer: subOrgNum } = request.params.arguments as { organisasjonsnummer: string };
      const subEntity = await apiClient.getSubEntity(subOrgNum);
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(subEntity, null, 2),
          },
        ],
      };
Behavior2/5

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

With no annotations provided, the description carries full burden but only states it 'gets detailed information' without specifying what 'detailed' includes, whether it's read-only, requires authentication, has rate limits, or returns structured data. This leaves significant behavioral gaps for a tool with unknown operational characteristics.

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 directly states the tool's purpose without unnecessary words. It's appropriately sized and front-loaded with the core action, making it easy to parse quickly.

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

Completeness2/5

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

For a tool with no annotations, no output schema, and multiple sibling tools, the description is insufficient. It doesn't explain what 'detailed information' entails, how it differs from similar tools, or any behavioral constraints, leaving the agent with inadequate context to use it effectively.

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 the parameter 'organisasjonsnummer' is documented in the schema as a '9-digit organization number'. The description adds no additional parameter semantics beyond implying it identifies a 'specific Norwegian business sub-entity', which aligns with but doesn't extend the schema.

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 sub-entity', making the purpose understandable. However, it doesn't explicitly differentiate from sibling tools like 'get_entity' or 'get_sub_entity_updates', which would require more specific scope clarification.

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?

No guidance is provided on when to use this tool versus alternatives like 'get_entity', 'search_sub_entities', or 'get_sub_entity_updates'. The description mentions 'specific' but doesn't clarify prerequisites or contextual triggers for choosing this tool over siblings.

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