Skip to main content
Glama

Companies connected through people

get_company_network
Read-onlyIdempotent

Find companies linked by shared officers or owners to trace group structures and beneficial-ownership relationships.

Instructions

Companies connected to this one through shared officers or owners (one hop). Use for group structure and beneficial-ownership tracing. Person names are gated like everywhere else.

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

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
dataNoConnected companies and the people linking them.
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": "Connected companies and the people linking them."
      +    },
      +    "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.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description adds genuinely useful behavioral context beyond that: person names are access-gated and FO data requires an attested purpose, which tells the agent about permission constraints it could not infer from annotations.

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 short sentences, front-loaded with the core scope, then usage, then the access caveat. No filler and nothing buried.

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?

An output schema exists, so return values need not be explained. Scope, use case and data-gating are covered; the main remaining gap is sibling differentiation from get_company_relations and any hint about result size or traversal limits for the one-hop expansion.

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 warning and the 'never guess purpose' instruction. The description adds only the 'one hop' traversal-depth hint, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific resource (companies connected through shared officers or owners) and scopes it with '(one hop)', which is concrete and actionable. However, it never distinguishes itself from the sibling get_company_relations, which sounds like it could cover similar graph traversal, leaving the agent to guess which to call.

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?

Gives explicit use cases: 'group structure and beneficial-ownership tracing'. That is clear when-to-use guidance, but there are no when-not conditions and no routing to alternatives such as get_company_relations or get_company_details.

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