Skip to main content
Glama

Check national company register

check_company_register
Read-onlyIdempotent

Looks up a company live in the official national company register of Norway (Brønnøysund Enhetsregisteret), Czechia (ARES), Finland (PRH / YTJ) or the United Kingdom (Companies House), by company number or by name (at most 10 matches). Returns name, legal form, address, registration date, state as the register says it ("active" only where the register says so, "registered" = entered and not deleted, "deleted"), bankruptcy, liquidation or restructuring as separate fields where the register publishes them, and whether the company is VAT registered (true, false, or null if the register says nothing). Each field appears only if the register provides it. Use it to confirm that a Norwegian, Czech, Finnish or British partner exists and is active.

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": {
      "country": "<country>"
    },
    "name": "check_company_register"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoCompany name to search for (at most 10 matches). Give number OR name.
numberNoThe national company number: NO organisation number (9 digits), CZ IČO (8 digits), FI Business ID / Y-tunnus (e.g. 0112038-9), GB company number (8 characters, e.g. 02050399 or SC002180). Give number OR name.
countryYesNO (Norway), CZ (Czechia), FI (Finland) or GB (United Kingdom).
with_receiptNoOptional, default false. Set true only when the user asks for a signed receipt of this check for their files.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / country / description
      Previous value: -"NO (Norway), CZ (Czechia) or FI (Finland)."New value: +"NO (Norway), CZ (Czechia), FI (Finland) or GB (United Kingdom)."
    • changedInput schema / properties / country / enum
      Previous value: -[
      -  "NO",
      -  "CZ",
      -  "FI"
      -]New value: +[
      +  "NO",
      +  "CZ",
      +  "FI",
      +  "GB"
      +]
    • changedInput schema / properties / number / description
      Previous value: -"The national company number: NO organisation number (9 digits), CZ IČO (8 digits), FI Business ID / Y-tunnus (e.g. 0112038-9). Give number OR name."New value: +"The national company number: NO organisation number (9 digits), CZ IČO (8 digits), FI Business ID / Y-tunnus (e.g. 0112038-9), GB company number (8 characters, e.g. 02050399 or SC002180). Give number OR name."
  2. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, yet the description still adds substantial behavior: the 10-match cap on name searches, per-register field availability ('Each field appears only if the register provides it'), explicit status semantics ('active' only where the register says so, 'registered' = entered and not deleted, 'deleted'), separate bankruptcy/liquidation/restructuring fields, and a tri-state VAT-registration value including null. What is missing is failure behavior (no match / invalid number) and what with_receipt actually produces.

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?

Front-loaded with the action and dense with useful detail; however, the list of countries appears twice ('of Norway..., Czechia..., Finland... or the United Kingdom' and later 'a Norwegian, Czech, Finnish or British partner'), which is removable redundancy in an otherwise single tight paragraph.

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 no output schema, the description carries the return-value burden and does so well: it names the returned fields, explains sparse responses, defines the status vocabulary and the tri-state VAT flag. Combined with a fully documented schema, an agent has everything needed to call and interpret the result.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3; the description adds meaning by mapping each country enum value to its concrete registry (NO→Brønnøysund Enhetsregisteret, CZ→ARES, FI→PRH/YTJ, GB→Companies House), which helps interpret results. It says nothing about the with_receipt parameter, so the added value is real but partial.

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?

States a specific verb and resource ('looks up a company live in the official national company register') and enumerates exactly which countries/registers are covered (Brønnøysund, ARES, PRH/YTJ, Companies House), which implicitly separates it from siblings like find_swiss_company and check_business_partner. An agent can route on the country coverage alone.

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?

'Use it to confirm that a Norwegian, Czech, Finnish or British partner exists and is active' gives a clear when-to-use context, and the country list scopes out non-covered jurisdictions such as Switzerland. It stops short of naming an alternative tool or stating when not to use it, so it falls short of a 5.

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