Skip to main content
Glama
reidar80

Norwegian Business Registry MCP Server

by reidar80

search_voluntary_organizations

Search Norway's voluntary organization registry to find registered entities, access organizational details, and retrieve governance data for non-profit research and verification.

Instructions

Search voluntary organizations in the voluntary organization registry

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
searchAfterNoSearch after this organization number for pagination
sizeNoMaximum number of organizations (default 100)
spraakNoLanguage for code descriptions (e.g., 'NOB')

Implementation Reference

  • The core handler function that executes the tool logic: makes an HTTP request to the Frivillighetsregisteret API endpoint for searching voluntary organizations using the provided parameters.
    async searchVoluntaryOrganizations(params: {
      searchAfter?: string;
      size?: number;
      spraak?: string;
    } = {}) {
      return this.makeRequest('/frivillighetsregisteret/api/frivillige-organisasjoner', params);
    }
  • Input schema definition for the search_voluntary_organizations tool, specifying optional parameters: searchAfter, size, and spraak.
    inputSchema: {
      type: "object",
      properties: {
        searchAfter: { type: "string", description: "Search after this organization number for pagination" },
        size: { type: "number", description: "Maximum number of organizations (default 100)" },
        spraak: { type: "string", description: "Language for code descriptions (e.g., 'NOB')" }
      }
    }
  • Registration of the tool in the ListToolsRequestHandler response array, defining name, description, and input schema.
      name: "search_voluntary_organizations",
      description: "Search voluntary organizations in the voluntary organization registry",
      inputSchema: {
        type: "object",
        properties: {
          searchAfter: { type: "string", description: "Search after this organization number for pagination" },
          size: { type: "number", description: "Maximum number of organizations (default 100)" },
          spraak: { type: "string", description: "Language for code descriptions (e.g., 'NOB')" }
        }
      }
    },
  • MCP server dispatch handler case that invokes the BrregApiClient.searchVoluntaryOrganizations method and formats the response as MCP content.
    case "search_voluntary_organizations":
      const voluntaryOrgs = await apiClient.searchVoluntaryOrganizations(request.params.arguments as any);
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(voluntaryOrgs, null, 2),
          },
        ],
      };
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 but only states the basic action. It doesn't mention whether this is a read-only operation, how results are returned (e.g., pagination details beyond the schema), potential rate limits, authentication needs, or error conditions. For a search 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 directly states the tool's purpose without any fluff or redundant information. It's appropriately sized and front-loaded, making it easy for an agent 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 the complexity of a search operation with three parameters, no annotations, and no output schema, the description is incomplete. It lacks information on what the search returns (e.g., organization details, match criteria), how results are structured, or any behavioral nuances. This leaves the agent with insufficient context to use the tool effectively beyond basic invocation.

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%, with all three parameters clearly documented in the input schema (searchAfter for pagination, size for result limits, spraak for language). The description adds no additional parameter semantics beyond what's already in the schema, so it meets the baseline for high schema coverage without compensating value.

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 ('Search') and target resource ('voluntary organizations in the voluntary organization registry'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'search_entities' or 'search_sub_entities' that might also search related data, missing an opportunity for clearer distinction.

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 'get_voluntary_organization' (which might retrieve a single organization) or other search tools in the sibling list. There's no mention of prerequisites, typical use cases, or exclusions, leaving the agent to infer usage context.

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