Skip to main content
Glama

get_company

Read-only

Look up a company in an official public EU business register in one call, any of the 27 EU states. Live open registers by ID or name: EE (with board members), FR (with directors), CZ, FI, PL (KRS number or NIP), LV, IE, HR (Sudski registar: OIB, MBS or full/partial name; no officers in the public API); DK (CVR via Datafordeler: CVR number or full registered name; no persons); AT (Firmenbuch via JustizOnline: FN such as 93363 z or a name; officers with representation rules, no birth dates); NL (KVK open dataset, free: basic data of BV and NV by KVK number only, no names or persons; names return the kvk.nl search link plus GLEIF LEI holders); LT, SE and SI from nightly snapshots of the official open bulk files (data_as_of in the answer). Other states return the official register lookup URL plus matching LEI holders from GLEIF. Any EU VAT number is checked live in VIES (id_type=vat or a prefixed number like DE123456789); LEIs via id_type=lei or country=EU. Every answer has source_url, licence and retrieved_at. Free, read-only.

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>",
      "query": "<query>"
    },
    "name": "get_company"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesRegistry code (EE 8 digits, FR SIREN, CZ IČO, FI Y-tunnus, PL KRS or NIP, LV 11 digits, LT 9 digits, SE organisationsnummer 10 digits, SI matična številka 7 or 10 digits, IE company number, HR OIB 11 digits or MBS, DK CVR 8 digits, NL KVK number 8 digits, AT Firmenbuchnummer e.g. FN 93363 z), VAT number, LEI or company name.
countryYesEU member state code (EE, FR, DE, ...; EL or GR for Greece), or EU for an LEI search.
id_typeNoOptional. vat = VIES check, lei = GLEIF. Default: detected from the query.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / query / description
      Previous value: -"Registry code (EE 8 digits, FR SIREN, CZ IČO, FI Y-tunnus, PL KRS or NIP, LV 11 digits, LT 9 digits, SE organisationsnummer 10 digits, SI matična številka 7 or 10 digits, IE company number, HR OIB 11 digits or MBS, DK CVR 8 digits, NL KVK number 8 digits), VAT number, LEI or company name."New value: +"Registry code (EE 8 digits, FR SIREN, CZ IČO, FI Y-tunnus, PL KRS or NIP, LV 11 digits, LT 9 digits, SE organisationsnummer 10 digits, SI matična številka 7 or 10 digits, IE company number, HR OIB 11 digits or MBS, DK CVR 8 digits, NL KVK number 8 digits, AT Firmenbuchnummer e.g. FN 93363 z), VAT number, LEI or company name."
  2. Changed1 schema field changed
    • changedInput schema / properties / query / description
      Previous value: -"Registry code (EE 8 digits, FR SIREN, CZ IČO, FI Y-tunnus, PL KRS or NIP, LV 11 digits, LT 9 digits, SE organisationsnummer 10 digits, SI matična številka 7 or 10 digits, IE company number, HR OIB 11 digits or MBS, DK CVR 8 digits), VAT number, LEI or company name."New value: +"Registry code (EE 8 digits, FR SIREN, CZ IČO, FI Y-tunnus, PL KRS or NIP, LV 11 digits, LT 9 digits, SE organisationsnummer 10 digits, SI matična številka 7 or 10 digits, IE company number, HR OIB 11 digits or MBS, DK CVR 8 digits, NL KVK number 8 digits), VAT number, LEI or company name."
  3. Changed1 schema field changed
    • changedInput schema / properties / query / description
      Previous value: -"Registry code (EE 8 digits, FR SIREN, CZ IČO, FI Y-tunnus, PL KRS or NIP, LV 11 digits, LT 9 digits, SE organisationsnummer 10 digits, SI matična številka 7 or 10 digits, IE company number, HR OIB 11 digits or MBS), VAT number, LEI or company name."New value: +"Registry code (EE 8 digits, FR SIREN, CZ IČO, FI Y-tunnus, PL KRS or NIP, LV 11 digits, LT 9 digits, SE organisationsnummer 10 digits, SI matična številka 7 or 10 digits, IE company number, HR OIB 11 digits or MBS, DK CVR 8 digits), VAT number, LEI or company name."
  4. Changed1 schema field changed
    • changedInput schema / properties / query / description
      Previous value: -"Registry code (EE 8 digits, FR SIREN, CZ IČO, FI Y-tunnus, PL KRS or NIP, LV 11 digits, LT 9 digits, IE company number, HR OIB 11 digits or MBS), VAT number, LEI or company name."New value: +"Registry code (EE 8 digits, FR SIREN, CZ IČO, FI Y-tunnus, PL KRS or NIP, LV 11 digits, LT 9 digits, SE organisationsnummer 10 digits, SI matična številka 7 or 10 digits, IE company number, HR OIB 11 digits or MBS), VAT number, LEI or company name."
  5. Changed1 schema field changed
    • changedInput schema / properties / query / description
      Previous value: -"Registry code (EE 8 digits, FR SIREN, CZ IČO, FI Y-tunnus, PL KRS or NIP, LV 11 digits, LT 9 digits, IE company number), VAT number, LEI or company name."New value: +"Registry code (EE 8 digits, FR SIREN, CZ IČO, FI Y-tunnus, PL KRS or NIP, LV 11 digits, LT 9 digits, IE company number, HR OIB 11 digits or MBS), VAT number, LEI or company name."
  6. Changed3 schema fields changed
    • changedInput schema / properties / country / description
      Previous value: -"ISO country code, e.g. EE."New value: +"EU member state code (EE, FR, DE, ...; EL or GR for Greece), or EU for an LEI search."
    • addedInput schema / properties / id_type
      Added value: +{
      +  "description": "Optional. vat = VIES check, lei = GLEIF. Default: detected from the query.",
      +  "enum": [
      +    "registry",
      +    "vat",
      +    "lei"
      +  ],
      +  "type": "string"
      +}
    • changedInput schema / properties / query / description
      Previous value: -"Registry code (EE: 8 digits) or company name."New value: +"Registry code (EE 8 digits, FR SIREN, CZ IČO, FI Y-tunnus, PL KRS or NIP, LV 11 digits, LT 9 digits, IE company number), VAT number, LEI or company name."
  7. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Beyond readOnlyHint/openWorldHint, it discloses unusually rich behaviour: which registers are live vs nightly snapshots ("data_as_of in the answer"), per-country data gaps ("no officers in the public API", "no persons", "no names or persons"), and the NL name-query side effect of returning a kvk.nl search link plus GLEIF LEI holders. It also states the cost and safety profile ("Free, read-only") and the guaranteed response envelope (source_url, licence, retrieved_at).

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

Conciseness3/5

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

The core capability is front-loaded, but the body is a single dense paragraph of parenthetical per-country caveats that is hard to scan and mixes coverage details with behavioural caveats. Most content earns its place, yet a bulleted structure would deliver the same information far more legibly.

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

Completeness4/5

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

For a 3-parameter, multi-jurisdiction lookup with no output schema, the description covers nearly everything needed: input formats, per-country limitations, snapshot freshness, and key response fields. The main residual gap is that the full response shape beyond source_url/licence/retrieved_at is not described.

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. The description still adds meaning: it clarifies accepted ID formats per country (PL KRS or NIP, HR OIB/MBS), that country=EU triggers an LEI search, and that a prefixed VAT number like DE123456789 is accepted without id_type. Default detection for id_type is also explained.

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 opening sentence states a specific verb and resource ("Look up a company in an official public EU business register") and immediately bounds scope to 27 EU states and a single call. No sibling tool is a lookup tool, so there is no confusion risk, and the per-country enumeration makes the supported coverage unambiguous.

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 gives clear context for selecting id_type: "Any EU VAT number is checked live in VIES (id_type=vat...)" and "LEIs via id_type=lei or country=EU". It also explains fallback behaviour for unlisted states, which is strong guidance. What's missing is explicit when-not guidance, e.g. when to prefer a name search over an ID search given the documented NL name limitation.

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