Skip to main content
Glama

Norwegian company officers and board

get_norwegian_company_officers
Read-only

Officers and board of a Norwegian company from the official Enhetsregisteret (Brønnøysundregistrene, NLOD 2.0), refreshed daily from the national roles bulk: general manager, board chair, deputy chair, members and deputies (with who elected them: shareholder class or employees), fully liable partners with their liability share, general partner, holder, licensed auditor and accountant with their own orgnr and licence status, Norwegian representative of a foreign entity. Current mandates by default; inclure_anciens=true adds deregistered roles, both counts stay exact. organe and role are closed lists with the register's code and wording (GET /v1/lecture); no appointment or end dates exist in the source. GDPR: natural persons come with first name, last name, role and deceased flag only — never the birth date the register publishes. Legal persons only: sole proprietorships, estates and unknown forms are refused (404, payment cancelled). A known legal person with no registered role gets aucun_mandat_inscrit: true. Paid via x402 ($0.01 in USDC or EURC).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes9-digit Norwegian organisasjonsnummer, no spaces, e.g. 923609016
api_keyNoOptional Sirenic API key (srn_live_…) to pay with prepaid credits instead of x402 — no wallet needed. Get one at https://api.sirenic.eu/compte. Ignored when x_payment is provided (the signed payment wins). On insufficient balance the tool returns a credits error, not an x402 quote.
x_paymentNoOptional signed x402 PAYMENT-SIGNATURE header value. Omit to receive the payment quote.
inclure_anciensNotrue to add deregistered (historical) mandates; default lists current mandates only

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
hintNoHow to settle the quote, present when payment_required is true.
quoteNoThe signable x402 payment requirements when payment_required is true: {x402Version, accepts[]} where each entry carries scheme, network, amount, asset and payTo (USDC and EURC options at the same numeric amount). Sign one entry and call again with `x_payment`.
resultatNoThe endpoint's JSON response when payment_required is false. Paid responses carry `source`, `disclaimer` and an Ed25519 signature, and every paid JSON response carries a `provenance` array (all tools since 2026-09-06) — one entry per block served, with the official register, licence, version, `as_of` date and `precision_as_of` (what that date means), plus the common per-block envelope: `etat` in a closed list (servi, absence_mesuree, absence_non_conclusive, partiel, perime, indisponible, sans_objet), `motif` when unavailable, `age_jours` (only for publication or ingestion dates), `couverture` (complete / partielle / non_mesurable with its measure) and `confiance` in bands (faible / moyenne / forte, only where a measure grounds it, never averaged across blocks). Read the states before the numbers: an absence_non_conclusive, indisponible or partiel block is never « nothing to report » — only absence_mesuree asserts an absence. Register codes: GET /v1/provenance/registres ; states, closed lists and reading rules: GET /v1/lecture (both free). The PDF tools carry no JSON envelope (the PDF report prints it).
payment_requiredYesTrue when this response is an x402 payment quote instead of data: settle one of the quote's `accepts` options and call the tool again with `x_payment`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Even with readOnlyHint and openWorldHint annotations, the description goes far beyond: daily refresh, 'inclure_anciens=true adds deregistered roles', closed vocabularies ('organe and role are closed lists... (GET /v1/lecture)'), absence of appointment/end dates, GDPR minimization (first/last name, role, deceased flag only), payment via x402, and 404 refusal behavior. No contradiction with annotations.

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

Conciseness4/5

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

The core purpose is front-loaded in the first sentence, followed by dense but relevant detail in a single paragraph. It is longer than necessary due to redundancy with the title (officers and board) and a few run-on clauses, but every sentence carries useful behavioral or legal information; no padding.

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 already present, the description does not need to describe return values. It covers source, refresh cadence, role taxonomy, GDPR handling, legal-form restrictions, empty-result signal (aucun_mandat_inscrit: true), absence of dates, and payment details, making the tool fully invocable without guesswork.

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 description coverage is 100%, so the schema already documents id, api_key, x_payment and inclure_anciens. The description reinforces the inclure_anciens behavior ('adds deregistered roles, both counts stay exact') and gives cost context for x402, but adds little per-parameter semantic beyond the schema; baseline 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 opens with the specific resource—'Officers and board of a Norwegian company'—and names the official source (Enhetsregisteret/Brønnøysundregistrene). It lists the exact officer types returned and distinguishes itself from sibling Norwegian tools by the role-focused scope and the legal-person restriction.

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?

It clearly states this tool is for officers/board of Norwegian legal persons, defaults to current mandates, and explains that sole proprietorships, estates and unknown forms are refused. It does not explicitly name alternative sibling tools for related data (e.g., accounts), but the context is clear enough that an agent can decide when to invoke it.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources