Skip to main content
Glama

Full company record

get_company_details
Read-onlyIdempotent

Retrieve a complete company record by national registry ID, including identity, address, legal status, NACE, LEI, NIS2, EU funds, and procurement data for KYB and due diligence.

Instructions

Full record for one company: identity, address, legal form, status flags, NACE, and the whole enrichment layer we hold (web, tech stack, NIS2, EU funds, LEI, HU de minimis state aid granted, HU public procurement from EKR, …). Large — prefer company_brief unless you need a specific field. Natural-person fields are gated and may be withheld; a withheld field is not the same as an empty one.

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": {
      "ico": "<ico>"
    },
    "name": "get_company_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
icoYesNational registry identifier (SK/CZ IČO, AT Firmenbuch number, PL KRS/REGON, FR SIREN, …). Leading zeros are normalised server-side.
countryNoISO 3166-1 alpha-2 country of the register (e.g. SK, CZ, AT, PL). Strongly recommended: registry numbers are NOT unique across countries (an SK and a CZ company can share the same 8-digit IČO), and without it the server picks one by tie-break.
purposeNoLegal purpose for natural-person (FO) data, attested by the account holder. Only needed when the API key has full FO access; must be one of the purposes licensed on the key. Never guess it — ask the user if it is not known.

Output Schema

NameRequiredDescriptionDefault
dataNoThe full company record.
metaNoRequest metadata: request_id (quote it in support requests), duration_ms, cached.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changedv0.2.2
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • changedInput schema / properties / country / description
      Previous value: -"ISO 3166-1 alpha-2 code of the register, e.g. SK or FR. REQUIRED for any market whose identifier is not a 6-8 digit IČO, and the only way to disambiguate an 8-digit IČO that exists in both SK and CZ."New value: +"ISO 3166-1 alpha-2 country of the register (e.g. SK, CZ, AT, PL). Strongly recommended: registry numbers are NOT unique across countries (an SK and a CZ company can share the same 8-digit IČO), and without it the server picks one by tie-break."
    • removedInput schema / properties / country / maxLength
      Removed value: -2
    • removedInput schema / properties / country / minLength
      Removed value: -2
    • addedInput schema / properties / country / pattern
      Added value: +"^[A-Za-z]{2}$"
    • changedInput schema / properties / ico / description
      Previous value: -"National registry identifier. Slovakia, Czechia and Estonia use a 6-8 digit IČO; France a 9-digit SIREN. Norway, Lithuania and Portugal 9 digits; Belgium 10; Switzerland CHE#########; Finland 0140168-2. Austria uses a Firmenbuch number like 357942k; Britain 08183069 or SC307270. Pass `country` for anything that is not a Slovak or Czech IČO."New value: +"National registry identifier (SK/CZ IČO, AT Firmenbuch number, PL KRS/REGON, FR SIREN, …). Leading zeros are normalised server-side."
    • removedInput schema / properties / ico / pattern
      Removed value: -"^[A-Za-z0-9][A-Za-z0-9./-]{0,31}$"
    • addedInput schema / properties / purpose
      Added value: +{
      +  "description": "Legal purpose for natural-person (FO) data, attested by the account holder. Only needed when the API key has full FO access; must be one of the purposes licensed on the key. Never guess it — ask the user if it is not known.",
      +  "enum": [
      +    "kyc",
      +    "aml",
      +    "credit",
      +    "risk_monitoring",
      +    "supplier_due_diligence",
      +    "prospection"
      +  ],
      +  "type": "string"
      +}
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "data": {
      +      "description": "The full company record."
      +    },
      +    "meta": {
      +      "description": "Request metadata: request_id (quote it in support requests), duration_ms, cached.",
      +      "type": "object"
      +    }
      +  },
      +  "type": "object"
      +}
  2. Changed5 schema fields changedv0.1.4
    • addedInput schema / properties / country
      Added value: +{
      +  "description": "ISO 3166-1 alpha-2 code of the register, e.g. SK or FR. REQUIRED for any market whose identifier is not a 6-8 digit IČO, and the only way to disambiguate an 8-digit IČO that exists in both SK and CZ.",
      +  "maxLength": 2,
      +  "minLength": 2,
      +  "type": "string"
      +}
    • changedInput schema / properties / ico / description
      Previous value: -"6-8 digit IČO (Slovak/Czech/Estonian registry number). Leading zeros optional."New value: +"National registry identifier. Slovakia, Czechia and Estonia use a 6-8 digit IČO; France a 9-digit SIREN. Norway, Lithuania and Portugal 9 digits; Belgium 10; Switzerland CHE#########; Finland 0140168-2. Austria uses a Firmenbuch number like 357942k; Britain 08183069 or SC307270. Pass `country` for anything that is not a Slovak or Czech IČO."
    • changedInput schema / properties / ico / maxLength
      Previous value: -8New value: +32
    • changedInput schema / properties / ico / minLength
      Previous value: -6New value: +1
    • changedInput schema / properties / ico / pattern
      Previous value: -"^\\d{6,8}$"New value: +"^[A-Za-z0-9][A-Za-z0-9./-]{0,31}$"
  3. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly/ idempotent/ non-destructive/ closed-world, so the safety profile is covered. The description adds real behavioral context beyond them: the payload is large (latency/size cost) and natural-person fields are gated by licence and may be withheld, with an explicit warning not to interpret withholding as absence.

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-loads the core purpose in the first clause and keeps total length to three sentences. The parenthetical enumeration of enrichment layers is long, and slightly redundant given an output schema exists, but it earns its place by signalling the tool's breadth.

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?

With an output schema present, the return format needn't be explained, and annotations carry the safety profile. The description still covers the decision-relevant points: size, scope of enrichment, and the gated-field caveat. Minor omission is any mention of the country parameter's importance, though the schema covers it.

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 ico, country, and purpose thoroughly (including the country tie-break and the 'never guess' warning). The description adds no parameter-level meaning beyond what the schema provides, so the baseline 3 applies.

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 ('Full record for one company') and enumerates the contents (identity, address, legal form, status flags, NACE, enrichment layers), so an agent knows exactly what it returns. It also explicitly names the sibling it overlaps with (company_brief), which distinguishes it from the other 12 tools in the list.

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?

'Prefer company_brief unless you need a specific field' gives an explicit when-to-use and when-not with the named alternative. It also adds a usage caveat about gated natural-person fields and the fact that withheld is not the same as empty, which prevents a common misreading of the response.

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