Skip to main content
Glama

Search companies in Norway, Finland, Czechia and Poland

company_registry
Read-only

Companies from the official registers of Norway, Finland, the Czech Republic and Poland. Search by name (Norway, Finland, Czech Republic) or look up one company by its number: Norway 9 digits, Finland Y-tunnus, Czech IČO, Poland KRS (Poland by number only). Answers give name, id, status, legal form, address, incorporation date and industry; Norway lookups by number also list managers. France: use /api/company/fr. Related tools on this server, for a different need: company_fr when you need to search French companies by name or SIREN/SIRET; company_br when you need to return Brazilian company data from BrasilAPI: legal name. Price: $0.003 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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": "company_registry"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoCompany name (not Poland)
idNoRegistry number: Norway 9 digits, Finland 1234567-8, Czech 8 digits, Poland 10-digit KRS
countryYesno, fi, cz or pl

Output Schema

NameRequiredDescriptionDefault
queryNo
sourceNo
countryNo
checkedAtNo
companiesNo
attributionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered; the description adds genuinely new behavior: the exact return fields (name, id, status, legal form, address, incorporation date, industry), the Norway-only manager listing, and the pricing model ($0.003 per successful call via x402, failures not charged). The payment/charge policy is the kind of context annotations cannot convey.

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?

Capability and country modes are front-loaded, and the pricing and sibling-routing sentences are separated at the end where they belong. The middle section is dense and semi-colon heavy, but no sentence is filler.

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, return values need not be explained, yet the description still names the fields and the Norway-specific manager data. Combined with per-country identifier formats, alternatives, and cost, an agent has everything needed to call it correctly.

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 the baseline is 3, but the description adds registry-specific formats beyond the schema: Norway 9 digits, Finland Y-tunnus, Czech IČO, Poland 10-digit KRS, and the Poland-by-number-only constraint on 'q'. The overlap with the schema's own q/id descriptions keeps it from a 5.

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 a specific verb and resource: search companies from the official registers of Norway, Finland, Czech Republic and Poland. It goes further by spelling out the two distinct modes (name search in NO/FI/CZ, number lookup in all four, Poland number-only), and it explicitly separates itself from company_fr and company_br.

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 states when to use this tool (search by name in Norway/Finland/Czechia, look up by number in any of the four), when not to use it (Poland name search is unsupported; France should go to /api/company/fr), and names the alternative siblings company_fr and company_br with the conditions that select them.

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