Skip to main content
Glama
reidar80

Norwegian Business Registry MCP Server

by reidar80

get_sub_entity_updates

Retrieve updates on subsidiary entities to maintain an accurate local copy of the Norwegian Business Registry.

Instructions

Get updates on sub-entities for maintaining a local copy of the registry

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
datoNoShow updates from this timestamp (ISO-8601)
oppdateringsidNoShow updates from this update ID
organisasjonsnummerNoFilter by organization numbers
pageNoPage number
sizeNoPage size (default 20, max 10000)
sortNoSort by ID (ASC/DESC)

Implementation Reference

  • Core handler function in BrregApiClient that executes the tool logic by making an HTTP request to the BRREG API for sub-entity updates.
    async getSubEntityUpdates(params: {
      dato?: string;
      oppdateringsid?: string;
      organisasjonsnummer?: string[];
      page?: number;
      size?: number;
      sort?: string;
    } = {}) {
      return this.makeRequest('/enhetsregisteret/api/oppdateringer/underenheter', params);
    }
  • Tool registration in the ListTools response, including name, description, and input schema.
    {
      name: "get_sub_entity_updates",
      description: "Get updates on sub-entities for maintaining a local copy of the registry",
      inputSchema: {
        type: "object",
        properties: {
          dato: { type: "string", description: "Show updates from this timestamp (ISO-8601)" },
          oppdateringsid: { type: "string", description: "Show updates from this update ID" },
          organisasjonsnummer: { type: "array", items: { type: "string" }, description: "Filter by organization numbers" },
          page: { type: "number", description: "Page number" },
          size: { type: "number", description: "Page size (default 20, max 10000)" },
          sort: { type: "string", description: "Sort by ID (ASC/DESC)" }
        }
      }
    },
  • Input schema definition for the get_sub_entity_updates tool, specifying parameters and types.
    inputSchema: {
      type: "object",
      properties: {
        dato: { type: "string", description: "Show updates from this timestamp (ISO-8601)" },
        oppdateringsid: { type: "string", description: "Show updates from this update ID" },
        organisasjonsnummer: { type: "array", items: { type: "string" }, description: "Filter by organization numbers" },
        page: { type: "number", description: "Page number" },
        size: { type: "number", description: "Page size (default 20, max 10000)" },
        sort: { type: "string", description: "Sort by ID (ASC/DESC)" }
      }
    }
  • Dispatch handler in the MCP CallToolRequestSchema that invokes the apiClient method and formats the response.
    case "get_sub_entity_updates":
      const subEntityUpdates = await apiClient.getSubEntityUpdates(request.params.arguments as any);
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(subEntityUpdates, 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 lacks behavioral details. It doesn't disclose whether this is a read-only operation, pagination behavior beyond schema hints, rate limits, authentication requirements, or what the updates contain. The phrase 'maintaining a local copy' implies incremental synchronization but isn't specific.

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. Every word earns its place—no redundancy or fluff. It's appropriately sized for a tool with good schema coverage.

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 6-parameter tool with no annotations and no output schema, the description is insufficient. It doesn't explain what 'updates' consist of, return format, error conditions, or how it fits with sibling tools. The schema covers parameters well, but behavioral and output context is missing.

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 fully documents all 6 parameters. The description adds no additional parameter semantics beyond implying temporal filtering ('updates') and registry context. Baseline 3 is appropriate since 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 verb ('Get updates') and resource ('on sub-entities'), and specifies the purpose ('for maintaining a local copy of the registry'). It distinguishes from siblings like 'get_sub_entity' (which likely retrieves static data) by focusing on updates, but doesn't explicitly differentiate from 'get_entity_updates' or 'get_role_updates'.

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_entity_updates', 'get_role_updates', or 'search_sub_entities'. It mentions the general purpose but offers no context about prerequisites, typical use cases, or exclusion criteria.

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