Skip to main content
Glama
Sign In
Brreg MCP Server

Brreg MCP Server

by daveHylde
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

get_municipality

Retrieve official details for any Norwegian municipality by entering its 4-digit municipality number. Access accurate registry data from Brønnøysundregistrene.

Instructions

Get specific municipality by municipality number

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "municipalityNumber": "<municipalityNumber>"
    },
    "name": "get_municipality"
  }
}

Input Schema

NameRequiredDescriptionDefault
municipalityNumberYesMunicipality number (4 digits)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations exist, so the description carries the full burden. It only says 'get' without disclosing return format, error behavior, read-only nature, or any limitations. This is minimal and not transparent.

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 extremely concise and front-loaded with the essential action and target. It is a single short sentence with no wasted words, satisfying conciseness requirements.

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?

With no output schema, no annotations, and minimal description, the agent lacks information about return values, possible errors, or expected usage context. This is insufficient for a complete understanding of the tool's behavior.

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 fully describes the single parameter (municipalityNumber with type string and explanation 'Municipality number (4 digits)'), so schema coverage is 100%. The description adds no additional meaning beyond that, giving the baseline score of 3.

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?

Description uses a clear verb 'Get' with a specific resource 'municipality' and specifies selection by municipality number. This distinguishes it from sibling 'get_municipalities' (plural) and other tools like 'get_company'.

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 about when to use this tool versus alternatives such as get_municipalities or search_companies. The description only states what it does, not when to prefer it.

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

Deploy Server

Other Tools