Skip to main content
Glama

Direct relations

get_company_relations
Read-onlyIdempotent

Retrieve a company's direct relations—statutory officers, owners, parents, subsidiaries, and M&A events—for KYB, KYC, due diligence, and risk checks without traversing the wider graph.

Instructions

Direct relations of one company — statutory officers, owners, parents, subsidiaries, M&A events — without traversing the wider graph. shareholders are owners only; members of the supervisory board are in supervisoryBoard. SK M&A events: effectiveDate is the date stated by the register; when missing, derivedEffectiveDate may carry a date INFERRED from the absorbed firm's deregistration (effectiveDateSource: "derived") — present it as an estimate, never as a register fact.

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_relations"
  }
}

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
dataNoOfficers, owners and corporate relations.
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#"
    • addedInput schema / properties / country
      Added value: +{
      +  "description": "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.",
      +  "pattern": "^[A-Za-z]{2}$",
      +  "type": "string"
      +}
    • changedInput schema / properties / ico / description
      Previous value: -"6-8 digit IČO (Slovak/Czech/Estonian registry number). Leading zeros optional. This endpoint is keyed on the legacy IČO column, so markets whose identifier is not a 6-8 digit IČO are not reachable through this endpoint yet."New value: +"National registry identifier (SK/CZ IČO, AT Firmenbuch number, PL KRS/REGON, FR SIREN, …). Leading zeros are normalised server-side."
    • changedInput schema / properties / ico / maxLength
      Previous value: -8New value: +32
    • changedInput schema / properties / ico / minLength
      Previous value: -6New value: +1
    • removedInput schema / properties / ico / pattern
      Removed value: -"^\\d{6,8}$"
    • changedInput schema / properties / purpose / description
      Previous value: -"Declared due-diligence purpose. Only needed for `full`-tier keys when the subject is a natural person (sole trader) — the API's FO gate refuses such subjects unless a recognised purpose is attested. Ignored for legal entities. Marketing/prospection is not a valid value here."New value: +"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."
    • changedInput schema / properties / purpose / enum
      Previous value: -[
      -  "kyc",
      -  "aml",
      -  "credit",
      -  "risk_monitoring",
      -  "supplier_due_diligence"
      -]New value: +[
      +  "kyc",
      +  "aml",
      +  "credit",
      +  "risk_monitoring",
      +  "supplier_due_diligence",
      +  "prospection"
      +]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "data": {
      +      "description": "Officers, owners and corporate relations."
      +    },
      +    "meta": {
      +      "description": "Request metadata: request_id (quote it in support requests), duration_ms, cached.",
      +      "type": "object"
      +    }
      +  },
      +  "type": "object"
      +}
  2. Changed1 schema field changedv0.1.4
    • changedInput schema / properties / ico / description
      Previous value: -"6-8 digit IČO (Slovak/Czech/Estonian registry number). Leading zeros optional."New value: +"6-8 digit IČO (Slovak/Czech/Estonian registry number). Leading zeros optional. This endpoint is keyed on the legacy IČO column, so markets whose identifier is not a 6-8 digit IČO are not reachable through this endpoint yet."
  3. First observedv0.1.0

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower, and the description still adds substantial interpretation context: the shareholders-vs-supervisoryBoard field distinction and, critically, that derivedEffectiveDate is an INFERRED value (effectiveDateSource: "derived") that must be presented as an estimate, not a register fact. That provenance caveat is exactly the kind of behavior annotations cannot express.

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?

Three sentences, all information-bearing, with the scope statement front-loaded ahead of the field-naming and data-provenance caveats. No restatement of the name, title, or annotations.

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?

For a read-only lookup with an output schema, the description supplies everything the schema cannot: what relation types are in scope, how it differs from the network tool, field-level semantics for shareholders/supervisoryBoard, and the inferred-date caveat. Nothing an agent needs to call or interpret it correctly is missing.

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 coverage is 100%, so ico, country (tie-break warning), and the purpose enum are already fully documented in the schema. The description adds no parameter-level syntax, format, or default information beyond that, 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?

The description names a specific verb+resource ('Direct relations of one company') and enumerates exactly what is returned: statutory officers, owners, parents, subsidiaries, M&A events. The phrase 'without traversing the wider graph' implicitly separates it from the graph-traversal sibling (get_company_network), so an agent can route without opening either schema.

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 selection context — use this for one company's direct ties rather than the wider network — which is enough to choose it over get_company_network. It stops short of naming that alternative explicitly or stating when a different tool (e.g. get_company_details, advanced_search) would be preferred.

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