Firmaradar

Overview Schema Source Related Servers Discussions Admin

Get Company Roles

firmaradar_get_company_roles

Read-onlyIdempotent

Retrieve board members, CEOs, signatories, and auditors for Norwegian companies from official BRREG records. Includes historic roles, role types, and appointment dates.

Instructions

List board members, daglig leder, signature holders, prokura and revisor for a Norwegian company. Set include_historic=true for people who previously held roles. Use when the user asks 'who runs X AS?' or 'who is on the board?' Roles come live from BRREG (the official enterprise register) and include role type and available appointment or resignation dates.

Input Schema

TableJSON Schema

Name	Required	Description
`orgnr`	Yes	9-digit orgnr.
`role_type`	No	Filter on a single role type. Omit to get all roles.
`include_historic`	No	Include roles that have ended.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`orgnr`	Yes
`roles`	Yes
`total_count`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.1.2Jul 31, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$defs": {
+    "CompanyRole": {
+      "properties": {
+        "fodselsaar": {
+          "anyOf": [
+            {
+              "type": "integer"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "default": null,
+          "title": "Fodselsaar"
+        },
+        "fra_dato": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "default": null,
+          "title": "Fra Dato"
+        },
+        "navn": {
+          "title": "Navn",
+          "type": "string"
+        },
+        "role_person_id": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "default": null,
+          "description": "Stable ID — pass to `get_person_roles` for more.",
+          "title": "Role Person Id"
+        },
+        "rolle_type": {
+          "title": "Rolle Type",
+          "type": "string"
+        },
+        "signatur_alene": {
+          "anyOf": [
+            {
+              "type": "boolean"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "default": null,
+          "title": "Signatur Alene"
+        },
+        "til_dato": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "default": null,
+          "title": "Til Dato"
+        }
+      },
+      "required": [
+        "rolle_type",
+        "navn"
+      ],
+      "title": "CompanyRole",
+      "type": "object"
+    }
+  },
+  "properties": {
+    "orgnr": {
+      "title": "Orgnr",
+      "type": "string"
+    },
+    "roles": {
+      "items": {
+        "$ref": "#/$defs/CompanyRole"
+      },
+      "title": "Roles",
+      "type": "array"
+    },
+    "total_count": {
+      "title": "Total Count",
+      "type": "integer"
+    }
+  },
+  "required": [
+    "orgnr",
+    "roles",
+    "total_count"
+  ],
+  "type": "object"
+}

First observedv0.1.0May 29, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Beyond the readOnlyHint/idempotentHint annotations, the description reveals that roles come live from BRREG (official enterprise register) and include appointment/resignation dates. This adds meaningful behavioral context not available in the annotations.

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 three sentences with no fluff: it states what is returned, how to get historic roles, and when to use it, plus a note on the data source. Every sentence earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, the description covers the essential context: purpose, example triggers, a parameter usage tip, and the live BRREG data source. It is complete for this tool's simplicity and leaves deeper return details to the output schema.

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 coverage is 100% and each parameter already has a clear description (9-digit orgnr, role_type filter, include_historic boolean). The description adds minimal extra value by rephrasing include_historic as 'people who previously held roles', but does not meaningfully enhance the schema-provided 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 clearly states the tool lists specific roles (board members, daglig leder, signature holders, prokura, revisor) for a Norwegian company. This specific verb+resource combination distinguishes it from general company lookup tools like firmaradar_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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit user query examples ('who runs X AS?', 'who is on the board?') for when to use the tool. It also gives a conditional for using include_historic, but does not mention when not to use it or alternative 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