Skip to main content
Glama

registry-mcp — national company registries

by io.github.foretak
OverviewDiscussionsAdmin

Search a national company register by name

search_company
Read-onlyIdempotent

Search a national company register by name, when you have a name rather than an identifier.

country="NO" searches Brønnøysundregistrene / Enhetsregisteret (brreg) — the norway company lookup for the norwegian business registry when the organisasjonsnummer (orgnr, org.nr) is not yet known; country="GB" is the uk company search at Companies House, returning each hit's company number (company registration number, CRN).

Sweden cannot be searched by name. Bolagsverket's free API has four operations and none takes a company name, so country="SE" raises not_implemented — a fact about the register, not a temporary gap, and it will not start working. Sweden supports lookup by identifier only: call lookup_company with the ten-digit organisationsnummer (or a sole trader's twelve-digit personnummer), or validate_company_id first to check the shape for free. Bolagsverket publishes the whole register as bulk downloadable files for callers who must search by name.

Then call lookup_company with the id of the right hit for the full report — a search hit is deliberately thin (name, legal form, status, city) and must not be acted on directly. Hits arrive in the register's own relevance order, so read each hit's confidence rather than assuming the first row is best. Zero hits is not an error, and hint says what to try next — Norwegian names are registered upper-case and often carry an 'AS', 'ASA' or 'NUF' suffix, UK names a 'LIMITED', 'LTD', 'PLC' or 'LLP' one, worth dropping before concluding a company does not exist.

Errors are the {"error": {"code", "message", "hint"}} envelope this server's instructions set out code by code; hint names the next call. Call list_countries if you are unsure a country is supported.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesCompany name to search for, free text — not an identifier. Use lookup_company once you have the id of the right hit.
limitNoMaximum hits to return, 1-100; default 10. Outside that range is a bad_request, not a silent clamp.
countryNoISO-3166-1 alpha-2 — NO Norway, GB United Kingdom, SE Sweden. UK is not a country code here and is rejected. Call list_countries for the live set.NO

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
hintNoWhat to do next, e.g. 'call lookup_company with the id of the right hit'.
hitsNoBest matches, best first: always sorted by `confidence` descending. Hits that score equally keep the order the upstream register returned them in.
queryYesThe name that was searched for.
totalNoTotal matches upstream, which may exceed len(hits).
cachedNoServed from cache.
countryYesISO-3166-1 alpha-2, upper-case.
registryYesRegistry slug.
truncatedNoTrue when `total` exceeds the returned hits.
fetched_atNoUTC timestamp of the fetch.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / country / description
      Previous value: -"ISO-3166-1 alpha-2 country code. 'NO' = Norway (Brønnøysundregistrene / Enhetsregisteret), 'GB' = United Kingdom (Companies House), 'SE' = Sweden (Bolagsverket). 'UK' is not a country code here and is rejected. Call list_countries for the current set rather than hard-coding one."New value: +"ISO-3166-1 alpha-2 — NO Norway, GB United Kingdom, SE Sweden. UK is not a country code here and is rejected. Call list_countries for the live set."
    • removedInput schema / properties / country / examples
      Removed value: -[
-  "NO",
-  "GB",
-  "SE"
-]
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum hits to return. 1-100, default 10; a value outside that range is a bad_request, not a silent clamp."New value: +"Maximum hits to return, 1-100; default 10. Outside that range is a bad_request, not a silent clamp."
  2. Changed2 schema fields changed
    • changedInput schema / properties / country / description
      Previous value: -"ISO-3166-1 alpha-2 country code. 'NO' = Norway (Brønnøysundregistrene / Enhetsregisteret), 'GB' = United Kingdom (Companies House). 'UK' is not a country code here and is rejected. Call list_countries for the current set rather than hard-coding one."New value: +"ISO-3166-1 alpha-2 country code. 'NO' = Norway (Brønnøysundregistrene / Enhetsregisteret), 'GB' = United Kingdom (Companies House), 'SE' = Sweden (Bolagsverket). 'UK' is not a country code here and is rejected. Call list_countries for the current set rather than hard-coding one."
    • changedInput schema / properties / country / examples
      Previous value: -[
-  "NO",
-  "GB"
-]New value: +[
+  "NO",
+  "GB",
+  "SE"
+]
  3. First observed

TDQS

A5/5.0
Behavior5/5

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

Beyond the annotations, the description discloses multiple non-obvious behaviors: search hits are deliberately thin and must not be acted on directly; relevance order is register-defined and confidence should be read rather than assuming the first hit; zero hits is not an error; errors use the standard envelope; and country=SE raises a permanent not_implemented. This goes well beyond the structured metadata.

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 long but dense and exceptionally well structured: it starts with the core purpose, then organizes by country, then covers behavior and error handling. Every sentence carries operational relevance, and no filler is present.

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?

Given the tool has three parameters, country-specific behavior, a non-trivial error contract, and a requirement to hand off to lookup_company, the description is thorough. It explains zero-hit behavior, hit confidence, naming suffix pitfalls, and the follow-up flow, so an agent has everything needed to invoke it correctly without further research.

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

Parameters5/5

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

Schema coverage is already 100%, but the description adds important semantic nuance: name is free text and not an identifier, limit outside 1-100 produces bad_request rather than a silent clamp, and country must be ISO-3166-1 alpha-2 with a specific caveat that 'UK' is rejected and SE is unsupported. This is strong added meaning beyond the input schema.

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 states a specific verb and resource: search a national company register by name, and explicitly distinguishes this from identifier lookup via lookup_company. It also separates the national registers by country, so an agent can immediately tell this tool apart from its siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

It gives clear when-to-use guidance: 'when you have a name rather than an identifier.' It also names alternatives — lookup_company, validate_company_id, list_countries — and explicitly warns that Sweden cannot be searched by name and requires lookup_company. This exceeds mere context and gives concrete routing rules.

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

All registry-mcp — national company registries toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources