Brreg MCP Server

get_municipalities

Fetch Norwegian municipalities with pagination and sorting. Use it to populate dropdowns or validate municipal codes.

Instructions

Get all municipalities

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_municipalities"
  }
}

Input Schema

Name	Required	Description
`page`	No	Page number (default: 1)
`size`	No	Page size (default: 20)
`sort`	No	Sort field and order (e.g., navn,ASC or navn,DESC)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 2, 2026

TDQS

B3/5.0

Behavior2/5

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It only states 'Get all municipalities' without revealing pagination behavior, result ordering, response format, or any limits. The schema implies pagination via page/size, but the description is silent on this, making 'all' potentially misleading.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely short and to the point, but it is under-specified for a tool with pagination and sorting parameters. While concise, it sacrifices necessary context, so it does not earn a higher score.

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 presence of pagination and sorting parameters, no output schema, and no annotations, the description is incomplete. It fails to explain that the result is paginated, what fields are returned, or how sorting affects the output, leaving significant gaps for an agent using this tool.

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?

All three parameters (page, size, sort) have descriptions in the schema, achieving 100% coverage. The tool description adds no additional semantic value beyond what the schema already provides, so the baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Get all municipalities' uses a specific verb (Get) and resource (municipalities), and the word 'all' distinguishes it from sibling get_municipality, which targets a single entity. This clearly states the tool's primary action and scope.

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 given on when to use this tool versus alternatives like get_municipality or search_municipalities. The description does not mention any conditions, prerequisites, or scenarios where it is preferred.

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

Deploy Server