Skip to main content
Glama

List the officers (directors, secretaries) of a company

get_officers
Read-onlyIdempotent

Retrieve current and historical company officers from official government registries worldwide, including directors, secretaries, and signatories. Supports cross-company tracing via officer IDs, filtering by active status, and deduplication by person.

Instructions

Return the officers of a company — current directors, secretaries, members, partners, board members, procurists / authorised signatories, liquidators, and (by default, where upstream exposes them) historical resignations.

Each officer has a unified shape (jurisdiction, officer_id, name, role, appointed_on, resigned_on, is_active) plus a jurisdiction_data object carrying the raw upstream fields verbatim. Role labels are passed through in the registry's native language (e.g. Styremedlem, Předseda představenstva, Président, PREZES ZARZĄDU) — translate client-side as needed. Birth-date precision varies by jurisdiction (some registries publish YYYY-MM-DD, some only month + year, some nothing).

officer_id, when present, can be passed to get_officer_appointments to retrieve every other company this person has been appointed to — cross-company tracing is one of the most powerful uses of this tool. Not every jurisdiction issues stable person IDs; corporate officers are usually keyed by the corporate's own company_id, natural persons may be keyed by a synthetic index. Some registries mask officer names under GDPR / privacy rules — that masking is upstream, not server-side.

Flags: include_resigned (default true) toggles historical entries on jurisdictions that expose both; group_by_person deduplicates the same person across consecutive appointments on jurisdictions that support it; fresh: true bypasses the cache. Flags are ignored on registries that don't support them. Jurisdictions that don't publish officer data (or that gate it behind paid extracts) return 501.

Per-country caveats (role-label vocabulary, birth-date precision, resignation coverage, GDPR masking, 501 gating, delta-vs-snapshot semantics) are available on demand — call list_jurisdictions({jurisdiction:"<code>"}) for the full schema, or list_jurisdictions({supports_tool:"get_officers"}) for the country-support matrix. All registries are official government sources.

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_resignedNoInclude officers who have resigned. Default true. Set to false to get only currently serving officers.
group_by_personNoCZ only. When true, dedupe the same person across multiple appointments (e.g. board member → chair → vice-chair) into a single entry. Identity key is (name + datumNarozeni for natural persons, or pravnickaOsoba.ico for corporate). Each grouped entry's jurisdiction_data._appointments[] lists all roles with their dates. Default false (returns one entry per appointment, matching GB behaviour).
freshNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
queried_atYesISO-8601 + Europe/London timezone stamp for when the registry was queried.
officersNo
itemsNo
dataNoAdapter returns a bare array; textResult() wraps under `data`.
total_countNo
next_cursorNo
Behavior5/5

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

Annotations already mark readOnlyHint: true and destructiveHint: false, but the description adds extensive behavioral context: return shape, native language role labels, birth-date precision variation, officer_id semantics, aggregated vs. per-appointment grouping, cache bypass, flag ignorance, and 501 responses for unsupported jurisdictions. No contradictions with annotations.

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?

The description is well-structured with clear sections and front-loads the main purpose. At several paragraphs, it is slightly verbose for a concise tool description, but every sentence adds value (e.g., cross-company tracing, per-country caveats). Could be tightened slightly without losing clarity.

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?

Given the tool's complexity (5 parameters, multiple jurisdictions, output schema exists), the description covers the return schema, parameter semantics, jurisdiction-specific caveats, error cases (501, GDPA masking), and cross-references to sibling tools for escalation. The output schema exists, so explicit return value explanation is unnecessary.

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 60%, leaving some parameters (company_id, fresh) without schema-level descriptions. The description compensates by clearly explaining include_resigned (default true, toggles historical entries), group_by_person (CZ-only deduplication), and fresh (bypass cache). It adds meaning beyond the schema by clarifying defaults and jurisdiction-specific behavior.

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 specifies a clear verb ('Return') and resource ('officers of a company'), and enumerates the types of officers (directors, secretaries, etc.) and fields returned, distinguishing it from sibling tools like 'get_officer_appointments', 'search_officers', and 'get_company_profile'.

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?

The description provides explicit guidance on when to use this tool (e.g., for cross-company tracing via officer_id), what parameters do (include_resigned, group_by_person, fresh), and caveats for jurisdictions (GDPR masking, 501 gating). It also directs users to list_jurisdictions for full capability details, effectively managing expectations.

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