companies-house-screening-mcp

Get filing history

get_filing_history

Read-onlyIdempotent

Check a company's filing history to see if accounts and confirmation statements are filed on time, and track officer or address changes or a competitor's filing cadence.

Instructions

What a company has filed and when — accounts, confirmation statements, officer changes, mortgages, address changes. Use it to judge whether a company is filing on time, to see when accounts were last made up, or to watch a competitor's filing cadence. Descriptions come back as Companies House template keys such as accounts-with-accounts-type-small, with their values alongside; the key is readable enough to interpret and is not translated here because a partial translation would render some filings wrongly. Filter with category to cut the volume. Needs a company number.

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.
`category`	No	Restrict to one category, e.g. accounts, confirmation-statement, officers, mortgage, address, capital, incorporation, resolution, insolvency.
`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.
`filings`	Yes
`pagination`	Yes	Where this page sits in the full result set.
`company_number`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.4.0Sep 5, 2026

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.2/5.0

Behavior4/5

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

The description adds genuine behavioral context beyond the read-only annotations by explaining that filing descriptions come back as un-translated Companies House template keys and why partial translation was avoided. It also hints at response volume by recommending category filtering, which is useful for an agent deciding how to call the tool.

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 compact and front-loaded: it states the core purpose first, then use cases, then an important output-format caveat, then a filtering tip. Every sentence earns its place without verbose framing or redundant schema repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the output schema and fully described input parameters, the description covers the important operational details: what filings are included, how keys are represented, why translation is skipped, and how to reduce volume. It could be slightly stronger by mentioning pagination behavior explicitly, but the start_index parameter and output schema already carry that burden.

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 description coverage is 100%, so the parameters are fully documented in the schema. The description adds only minimal parameter-related guidance, such as using category to cut volume and requiring a company number, which mostly restates what the schema already says.

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 opens with a specific statement of what the tool returns — "What a company has filed and when" — and lists concrete filing types such as accounts, confirmation statements, and officer changes. This clearly distinguishes it from sibling tools like get_company or get_officers by focusing on filing history events.

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?

It gives explicit use cases: judging whether a company files on time, seeing when accounts were last made up, and watching a competitor's filing cadence. It also notes the need for a company number and suggests filtering with category, though it does not explicitly name alternative tools or state when not to use it.

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

Deploy Server