Skip to main content
Glama

Get Company Officers

company_officers
Read-onlyIdempotent

Retrieve active directors, secretaries, and other officers for any UK company using its Companies House number. Includes appointment dates, nationality, and residence, excluding resigned officers.

Instructions

Fetch active officers for a Companies House company number.

Returns directors, secretaries, and other active officers with appointment dates, nationality, and country of residence. Resigned officers are excluded. Pagination is handled internally — do NOT pass items_per_page or start_index; this tool takes only company_number.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
company_numberYesCompanies House company number (8 digits, e.g. '03782379'). Returned by company_search.
items_per_pageNoIgnored — pagination is handled internally. Only accepted to avoid call failures.
start_indexNoIgnored — all officers are returned in one call.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
company_numberYesCompanies House company number.
include_resignedYesWhether resigned officers were included in this result.
totalYesTotal officers returned (filtered by include_resigned).
high_appointment_count_flagNoNumber of active officers with 10+ total appointments, or null if appointment counts were not fetched. Non-zero values are a nominee/phoenix director risk signal.
officersNoOfficer records.
Behavior4/5

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

Annotations already indicate readOnlyHint, idempotentHint, and non-destructive behavior. The description adds context about excluding resigned officers and internal pagination, which supplements the annotations without contradiction.

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 concise with two short paragraphs. The first sentence states the primary purpose, and the second provides necessary details. No unnecessary words.

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 presence of an output schema and thorough annotations, the description covers all essential aspects: purpose, data returned, exclusions, and parameter constraints. No gaps remain for an agent to infer.

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 descriptions cover 100% of parameters, so baseline is 3. The description reinforces that items_per_page and start_index are ignored, but does not add new semantic detail beyond what the schema provides. No additional parameter meanings are introduced.

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 fetches active officers for a Companies House company number, specifying what data is returned (directors, secretaries, appointment dates, nationality, country of residence) and what is excluded (resigned officers). It distinguishes from sibling tools by focusing solely on officers.

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?

The description explicitly warns against passing pagination parameters and states that only company_number is taken. This provides clear usage constraints, but it does not explicitly contrast with alternative sibling tools (e.g., company_profile) for when to use this tool versus others.

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/paulieb89/uk-due-diligence-mcp'

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