Skip to main content
Glama
reidar80

Norwegian Business Registry MCP Server

by reidar80

get_voluntary_organization

Retrieve detailed information about voluntary organizations using their 9-digit organization number from the Norwegian Business Registry.

Instructions

Get detailed information about a specific voluntary organization

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
organisasjonsnummerYes9-digit organization number
spraakNoLanguage for code descriptions (e.g., 'NOB')

Implementation Reference

  • Executes the "get_voluntary_organization" tool by parsing arguments, calling the API client, and returning the JSON response as text content.
    case "get_voluntary_organization":
      const { organisasjonsnummer: volOrgNum, spraak } = request.params.arguments as { organisasjonsnummer: string; spraak?: string };
      const voluntaryOrg = await apiClient.getVoluntaryOrganization(volOrgNum, { spraak });
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(voluntaryOrg, null, 2),
          },
        ],
      };
  • Input schema and metadata definition for the "get_voluntary_organization" tool, registered in the ListTools response.
    {
      name: "get_voluntary_organization",
      description: "Get detailed information about a specific voluntary organization",
      inputSchema: {
        type: "object",
        properties: {
          organisasjonsnummer: { type: "string", description: "9-digit organization number" },
          spraak: { type: "string", description: "Language for code descriptions (e.g., 'NOB')" }
        },
        required: ["organisasjonsnummer"]
      }
    },
  • BrregApiClient helper method that performs the HTTP request to the BRREG API for a specific voluntary organization's details.
    async getVoluntaryOrganization(orgNumber: string, params: { spraak?: string } = {}) {
      return this.makeRequest(`/frivillighetsregisteret/api/frivillige-organisasjoner/${orgNumber}`, params);
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states this is a 'Get' operation, implying read-only behavior, but doesn't disclose any behavioral traits such as authentication needs, rate limits, error conditions, or what 'detailed information' includes. For a tool with no 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 core purpose ('Get detailed information about a specific voluntary organization'). There is no wasted text, and it's appropriately sized for a simple lookup tool.

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?

Given no annotations and no output schema, the description is incomplete. It doesn't explain what 'detailed information' entails, potential response formats, or any behavioral aspects. For a tool with 2 parameters and no structured output documentation, more context is needed to be fully helpful.

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 schema already documents both parameters (organisasjonsnummer and spraak) with descriptions. The description adds no additional meaning beyond what the schema provides, such as examples or usage context. Baseline 3 is appropriate when 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 action ('Get detailed information') and target resource ('about a specific voluntary organization'), which distinguishes it from siblings like search_voluntary_organizations (which searches) and get_entity (which is more general). However, it doesn't explicitly differentiate from get_entity or other get_* tools beyond specifying 'voluntary organization'.

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. It doesn't mention when to choose this over get_entity (which might handle similar data) or search_voluntary_organizations, nor does it specify prerequisites or exclusions. The context is implied but not articulated.

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