Brreg MCP Server

get_company_updates

Fetch company updates from the Brønnøysundregistrene with optional filters for date, update ID, or organization numbers.

Instructions

Get updates for companies with optional filters

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_company_updates"
  }
}

Input Schema

Name	Required	Description
`date`	No	Show updates from and including this timestamp (ISO-8601: yyyy-MM-dd'T'HH:mm:ss.SSS'Z')
`page`	No	Page number (default: 1)
`size`	No	Page size (default: 20, max: 10000)
`sort`	No	Sort field and order (e.g., id,ASC or id,DESC). Only id is supported
`updateId`	No	Show only updates from and including update ID (>= 1)
`updatedBefore`	No	Show updates to and including this timestamp (ISO-8601: yyyy-MM-dd'T'HH:mm:ss.SSS'Z')
`includeChanges`	No	Include the changes that caused the update to be published
`organizationNumber`	No	Comma-separated list of organization numbers (9 digits each)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 2, 2026

TDQS

C2.9/5.0

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 only states that filters are optional, which is already apparent from the schema. It does not reveal whether the operation is read-only, how results are returned, or any pagination/sorting behavior beyond what the schema lists. This is a significant transparency gap.

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, short sentence with no redundant or extraneous information. It front-loads the primary purpose and everything stated is relevant. It is appropriately concise for the level of detail it provides.

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?

The tool has 8 parameters, no annotations, and no output schema. The description does not explain what the response contains, how updates are defined, or how the filters relate to each other. While the schema covers parameter formats, the description fails to provide essential high-level context needed for an agent to fully understand the tool's behavior and output.

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 base score is 3. The tool description itself adds no parameter-level meaning beyond what the schema already provides. It does not compensate for any gaps because there are none, but it also does not enhance understanding of the parameters.

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 uses a clear verb+resource pattern ('Get updates for companies'), immediately conveying the tool's function. It implicitly distinguishes from the sibling tool get_subunit_updates by specifying 'companies' rather than 'subunits', though it does not explicitly reference alternatives. The phrase 'with optional filters' adds a hint of flexibility without detail.

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_subunit_updates or search_companies. It does not offer any context about intended use cases, prerequisites, or exclusions. The only implied usage is from the resource name itself, which is not sufficient per the rubric.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server