companies-house-screening-mcp

Get company officers

get_officers

Read-onlyIdempotent

Retrieve current and resigned directors, secretaries, and members of a company. Use their officer IDs for conflict-of-interest checks across a board, or to see who runs the company.

Instructions

The directors, secretaries and members of one company, current and resigned, each with an officer_id you can pass to get_officer_appointments. Use it to see who runs a company, or as the first step in a conflict-of-interest check across a board. Service addresses are withheld unless verbose is set, because they are personal data and are rarely what the question needs. Needs a company number; call find_company first if you only have a name.

Input Schema

TableJSON Schema

Name	Required	Description
`verbose`	No	Also return the untouched Companies House payload under `raw`, alongside the shaped result. Roughly two and a half times the size; use it only when a field you need is missing from the shaped result.
`start_index`	No	Zero-based offset into the full result set. Use pagination.has_more to decide.
`company_number`	Yes	Eight-character Companies House number, such as 00000006 or SC123456. Leading zeros may be omitted. This tool does not accept a company name — call find_company first if that is all you have.
`items_per_page`	No	How many records to return. Defaults to the API default; the maximum is 100.

Output Schema

TableJSON Schema

Name	Required	Description
`raw`	No	The untouched Companies House payload. Present only when verbose was true.
`meta`	Yes	Provenance and budget for this answer.
`officers`	Yes
`pagination`	Yes	Where this page sits in the full result set.
`active_count`	No
`company_number`	Yes
`inactive_count`	No	Appointments that ended because the company did, rather than by resignation. Non-zero on a dissolved company, and the reason active + resigned can fall short of the total.
`resigned_count`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.4.0Sep 5, 2026

addedOutput schema / properties / inactive_count

Added value: +{
+  "description": "Appointments that ended because the company did, rather than by resignation. Non-zero on a dissolved company, and the reason active + resigned can fall short of the total.",
+  "type": "number"
+}

changedOutput schema / properties / meta / properties / licence / description

Previous value: -"Companies House data is Open Government Licence v3.0."New value: +"OGL v3.0 applies to eligible public-sector information. Personal data and other OGL exclusions are not licensed by this label; applicable data-protection duties still apply."

First observedv0.2.0Aug 30, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already mark the tool read-only and idempotent, and the description adds non-obvious behavior: service addresses are withheld for privacy unless verbose is set. It also discloses that verbose returns a much larger raw payload, which helps the agent set expectations beyond what the annotations convey.

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?

Four sentences, each earning its place: the tool's output, the use cases, the privacy caveat, and the prerequisite. The most actionable information is front-loaded, and there is no redundant wording.

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 an output schema present, the description does not need to explain return values. Combined with full schema documentation for all parameters, the description covers purpose, usage context, privacy behavior, and how to chain with sibling tools, so nothing critical is missing.

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 100%, which sets a baseline of 3. The description adds extra meaning for company_number by emphasizing it cannot be a name and requires find_company first, and for verbose by explaining the privacy trade-off. The remaining parameters are adequately documented in the schema.

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?

States a specific verb and resource: get officers of one company, including current and resigned. It also distinguishes itself from related siblings by noting each result carries an officer_id to pass to get_officer_appointments, making it clearly different from find_officer or get_officer_appointments.

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?

Explicitly gives when to use the tool: to see who runs a company or as the first step in a conflict-of-interest check. It also names the prerequisite (company number) and directs the agent to call find_company first if only a name is available.

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

Deploy Server