Skip to main content
Glama

Get company network (shared-officer graph)

get_company_network

Discover connected companies by entering an IČO. Returns current officers and, for each, other companies where the same person holds a role, with IČOs for walking the network further.

Instructions

Company-to-company network via shared people (statutory officers / shareholders). Returns the company's current officers and, for each, the OTHER companies where that same person also holds a role — every connected company carries its IČO so the graph is walkable. This is the primary network-walk primitive: feed a returned IČO back into get_company_network to traverse another hop. Empty result means the company has no current shared-officer edges (e.g. officer data not yet ingested for that entity) — it does NOT mean the company is isolated; try get_company_relations for UBO / M&A edges. Bearer-auth + FO-gated at the API: keys without an FO addendum are refused for natural-person sole traders.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
icoYes6-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.
purposeNoDeclared 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.
Behavior5/5

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

No annotations are provided, so the description carries full burden. It discloses the empty-result semantics (not isolated), the FO gate requirement for sole traders, bearer-auth requirement, and the walkable graph structure. This gives agents a realistic behavioral model.

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?

The description is detailed yet each sentence serves a purpose: functionality, usage, edge-case semantics, alternative guidance, and auth. Front-loaded with the core purpose and progressively adds nuance. No fluff.

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 complex graph-traversal tool with no output schema, the description covers return value structure, pagination-walkability, edge cases, and auth constraints. It is self-contained enough for an agent to use it correctly and know when to switch to another tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Even though the schema covers 100% of parameters, the description adds context beyond the schema for the 'purpose' parameter (only needed for natural-person sole traders, ignored for legal entities, marketing/prospection invalid). It also reinforces the 'ico' constraint about markets keyed on legacy IČO.

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 clearly states the tool's function: it builds a company-to-company network via shared officers/shareholders. It differentiates from siblings by explicitly positioning it as the 'primary network-walk primitive' and references get_company_relations for alternative edge types (UBO/M&A).

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?

Provides explicit when-to-use and alternatives: 'feed a returned IČO back into get_company_network to traverse another hop' and 'try get_company_relations for UBO / M&A edges'. Also clarifies the empty-result case with guidance to try another tool.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/juliusgerman/entyrix-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server