Skip to main content
Glama
reidar80

Norwegian Business Registry MCP Server

by reidar80

get_icnpo_categories

Retrieve ICNPO classification categories for non-profit organizations from the Norwegian Business Registry. Use this tool to access standardized international classifications for organizational categorization.

Instructions

Get ICNPO (International Classification of Non-Profit Organisation) categories

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
spraakNoLanguage for descriptions (e.g., 'NOB')

Implementation Reference

  • The core handler function implementing the logic for the 'get_icnpo_categories' tool by making an API request to the Brreg voluntary organizations registry endpoint.
    async getIcnpoCategories(params: { spraak?: string } = {}) {
      return this.makeRequest('/frivillighetsregisteret/api/icnpo-kategorier', params);
    }
  • Tool registration in the ListTools handler, defining the tool's name, description, and input schema.
    {
      name: "get_icnpo_categories",
      description: "Get ICNPO (International Classification of Non-Profit Organisation) categories",
      inputSchema: {
        type: "object",
        properties: {
          spraak: { type: "string", description: "Language for descriptions (e.g., 'NOB')" }
        }
      }
    }
  • JSON schema defining the input parameters for the tool (optional 'spraak' language parameter).
    inputSchema: {
      type: "object",
      properties: {
        spraak: { type: "string", description: "Language for descriptions (e.g., 'NOB')" }
      }
    }
  • Dispatch handler in the CallToolRequestSchema that invokes the tool's handler and formats the response as text content.
    case "get_icnpo_categories":
      const icnpoCategories = await apiClient.getIcnpoCategories(request.params.arguments as any);
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(icnpoCategories, null, 2),
          },
        ],
      };
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It states it 'gets' categories, implying a read-only operation, but doesn't disclose behavioral traits like rate limits, authentication needs, or response format. This is a significant gap for a tool with no annotation coverage.

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 with zero waste. It's appropriately sized and front-loaded, 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?

Given no annotations and no output schema, the description is incomplete. It doesn't explain what the tool returns (e.g., list structure, fields) or behavioral aspects, leaving gaps for a tool that likely outputs data.

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 schema description coverage is 100%, so the schema already documents the single parameter 'spraak' with its description. The description adds no additional meaning beyond what the schema provides, such as example values or constraints, resulting in a baseline score of 3.

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 ('ICNPO categories'), making the purpose understandable. It doesn't distinguish from siblings like 'get_organizational_form' or 'get_municipalities', which also retrieve categories/lists, so it lacks specific differentiation.

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. It doesn't mention prerequisites, context, or exclusions, leaving the agent to infer usage based on 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