Skip to main content
Glama

List the persons with significant control (beneficial owners) of a company

get_persons_with_significant_control
Read-onlyIdempotent

Retrieve persons with significant control (PSCs/beneficial owners) of a company from the statutory threshold register (typically >25% ownership or voting rights). Use for UBO, PSC, or control inquiries; for general shareholders, use the dedicated shareholders tool instead.

Instructions

Return the persons with significant control (PSCs / beneficial owners) of a company — persons on a statutory-threshold register (typically >25% ownership or voting rights).

When to call this tool. Only when the user explicitly asks about 'beneficial owners', 'UBO', 'PSC', 'who controls', or the >25% threshold register. For plain 'shareholders' / 'members' / '股东' / '持股人' questions, call get_shareholders instead — it is a DIFFERENT register (the full equity roster with no threshold). A 10% shareholder shows up on the members register but not here; a corporate trustee can show up here without being on the members register.

Each entry has name, kind (individual / corporate-entity / etc.), nature_of_control (e.g. ownership-of-shares-75-to-100-percent, voting-rights-25-to-50-percent), notified_on, and ceased_on if applicable. Raw upstream fields come through verbatim under jurisdiction_data. Returns an empty list (not an error) for companies whose registry supports PSCs but has no filing on record.

Many countries keep beneficial-ownership data in a separate register from the main company registry, or restrict it to authenticated / AML-obliged callers. Unsupported jurisdictions return 501, sometimes with alternative_tool='get_shareholders' when the caller probably wanted registered shareholders instead. Per-country availability, historical-entry behaviour, and paid-tier gates — call list_jurisdictions({jurisdiction:"<code>"}).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
jurisdictionYesISO 3166-1 alpha-2 country code (uppercase). All registries are official government sources. Currently supported: AU, BE, CA, CA-BC, CA-NT, CH, CY, CZ, DE, ES, FI, FR, GB, HK, IE, IM, IS, IT, KR, KY, LI, MC, MX, MY, NL, NO, NZ, PL, RU, TW. Per-country capability, ID format, examples, status mapping, and caveats: call `list_jurisdictions({jurisdiction:'<code>'})`. To find which countries support a specific tool: `list_jurisdictions({supports_tool:'<tool>'})`.
company_idYes
include_ceasedNoCZ only. Include historical PSCs (those with a ceased_on date). Default false. GB returns historical PSCs by default; CZ does not — set this to true to match GB behaviour.
freshNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
queried_atYesISO-8601 + Europe/London timezone stamp for when the registry was queried.
pscNo
itemsNo
dataNo
total_countNo
next_cursorNo
Behavior5/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, but description adds valuable context: returns empty list instead of error for no filings, distinguishes between registers, warns about jurisdiction-specific restrictions (501 errors, authentication needs), and points users to list_jurisdictions for more details. No contradiction with annotations; in fact, description aligns with idempotentHint and openWorldHint by noting jurisdiction-dependent behavior.

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?

Description is structured into logical sections with headings and bullet-point examples. Slightly long but every part adds value (usage guidance, register distinction, error handling, jurisdiction advice). Could be trimmed slightly on examples but remains informative.

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?

With output schema present, description fully covers behavioral nuances (empty list vs error, register differences, authentication needs, jurisdiction flexibility). Given server has sibling get_shareholders for contrast and list_jurisdictions for further info, description is complete.

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 description coverage is 50%, but description adds meaning beyond schema: explains jurisdiction parameter's role, caveats about supported countries, and advises using list_jurisdictions for details. For 'include_ceased', description clarifies it is CZ-specific and explains default behavior vs GB. However, 'fresh' parameter is not elaborated beyond schema's default.

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?

Description clearly states verb 'return', resource 'persons with significant control', and scope 'beneficial owners at >25% threshold'. Explicitly distinguishes from sibling 'get_shareholders' by identifying it as a different register.

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 criteria for when to call ('beneficial owners', 'UBO', 'PSC', >25% threshold) and when not to call (use get_shareholders instead). Names the alternative tool and explains register differences clearly.

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/sophymarine/openregistry'

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