Skip to main content
Glama
reidar80

Norwegian Business Registry MCP Server

by reidar80

get_organizational_form

Retrieve organizational form details from the Norwegian Business Registry using specific codes to identify company structures and legal entities.

Instructions

Get information about a specific organizational form

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
organisasjonskodeYesOrganizational form code (e.g., 'AS', 'ASA')

Implementation Reference

  • Handler logic for the 'get_organizational_form' tool. Extracts the 'organisasjonskode' parameter and delegates to BrregApiClient.getOrganizationalForm, returning the result as JSON text content.
    case "get_organizational_form":
      const { organisasjonskode } = request.params.arguments as { organisasjonskode: string };
      const orgForm = await apiClient.getOrganizationalForm(organisasjonskode);
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(orgForm, null, 2),
          },
        ],
      };
  • Registration of the 'get_organizational_form' tool in the ListTools response, including name, description, and input schema.
    {
      name: "get_organizational_form",
      description: "Get information about a specific organizational form",
      inputSchema: {
        type: "object",
        properties: {
          organisasjonskode: { type: "string", description: "Organizational form code (e.g., 'AS', 'ASA')" }
        },
        required: ["organisasjonskode"]
      }
    },
  • Core implementation in BrregApiClient that makes the HTTP GET request to the BRREG API endpoint for the specific organizational form using the provided code.
    async getOrganizationalForm(code: string) {
      return this.makeRequest(`/enhetsregisteret/api/organisasjonsformer/${code}`);
    }
  • Input schema definition for the 'get_organizational_form' tool, specifying the required 'organisasjonskode' string parameter.
    inputSchema: {
      type: "object",
      properties: {
        organisasjonskode: { type: "string", description: "Organizational form code (e.g., 'AS', 'ASA')" }
      },
      required: ["organisasjonskode"]
    }
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 the tool retrieves information, implying a read-only operation, but does not specify details like error handling, authentication needs, rate limits, or response format, which are critical for safe invocation.

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, direct sentence with no wasted words, making it easy to parse and front-loaded with the core action. It efficiently conveys the essential purpose without unnecessary elaboration.

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?

For a simple read tool with one well-documented parameter and no output schema, the description is minimally adequate but lacks depth. It does not explain what 'information' includes or behavioral traits, leaving gaps that could hinder effective tool selection and use.

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, clearly documenting the single required parameter 'organisasjonskode' with examples. The description adds no additional parameter semantics beyond what the schema provides, so it meets the baseline for adequate but unenhanced coverage.

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 ('information about a specific organizational form'), making the purpose understandable. However, it does not explicitly differentiate from sibling tools like 'get_organizational_forms' (plural), which might retrieve a list, leaving some ambiguity in scope.

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, such as 'get_organizational_forms' for multiple forms or other entity-related tools. It lacks context on prerequisites or exclusions, leaving the agent to infer usage from the name 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