Skip to main content
Glama
Sign In
Brreg MCP Server

Brreg MCP Server

by daveHylde
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

get_organization_forms_for_subunits

Retrieve legal organization forms applicable to subunits from the Norwegian Business Registry. Supports paginated, sorted queries to streamline compliance and registry lookups.

Instructions

Get organization forms for subunits

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

Input Schema

NameRequiredDescriptionDefault
pageNoPage number (default: 1)
sizeNoPage size (default: 20)
sortNoSort field and order (e.g., kode,ASC or kode,DESC)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.8/5.0
Behavior1/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 provides no information about pagination, data scope, return format, or any other behavioral traits beyond the basic action.

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 a single short sentence, which is concise, but it merely restates the tool name. It does not add structured context or earn its place beyond the name. It is under-specified rather than effectively concise.

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 tool's complexity (3 parameters, no output schema, no annotations), the description provides minimal context. It fails to explain what 'organization forms' are, how pagination works, or what the response looks like, leaving a significant gap for the agent.

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 parameters are fully documented in the schema. The description adds no additional meaning, but the baseline of 3 applies as the schema handles parameter semantics.

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 organization forms for subunits' clearly states the verb (Get) and the resource (organization forms for subunits), distinguishing it from sibling tools like 'get_organization_forms_for_units' and 'get_organization_forms'.

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 on when to use this tool versus alternatives. There is no mention of exclusions, prerequisites, or context for choosing this tool over sibling tools.

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