companies-house-mcp

list_filings

Read-onlyIdempotent

List a company's filings at Companies House, newest first, with form codes and descriptions. Filter by category like accounts or officers to quickly find specific documents.

Instructions

List what a company has filed at Companies House, newest first: accounts, confirmation statements, officer changes, charges, resolutions and so on, each with its form code and a readable description.

Use category rather than paging through everything. Document contents are not returned, only whether a copy exists.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Filings per page.
`category`	No	Only filings of this kind, e.g. 'accounts' or 'officers'. Omit for everything.
`start_index`	No	Offset for paging. Use next_start_index from a previous result.
`company_number`	Yes	Companies House company number, e.g. 00445790 or SC123456. Spaces and missing leading zeros are fine. Get it from search_companies if you only have a name.

Output Schema

TableJSON Schema

Name	Required	Description
`total`	Yes
`filings`	Yes	Newest first.
`category`	Yes
`company_number`	Yes
`next_start_index`	No	Pass this as start_index to get the next page. Null when there are no more results.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 23, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, and non-destructive behavior. The description adds observable behavioral detail beyond that: results are 'newest first,' each item includes a form code and readable description, and document contents are deliberately excluded. There is no contradiction with the annotations.

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: the first sentence states the core purpose and output, the second gives a filtering tip, and the third sets a scope boundary. Every sentence earns its place with no redundancy.

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 read-only annotations, full parameter documentation in the schema, and the presence of an output schema, the description covers the remaining essential behavior: ordering, result contents, filtering advice, and the non-return of document contents. Nothing needed to invoke the tool correctly 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 coverage is 100%, so the baseline is 3. The description adds a non-obvious parameter insight—'Use `category` rather than paging through everything'—which clarifies the relationship between category filtering and pagination beyond what the schema says.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific resource ('what a company has filed at Companies House') and a clear verb ('List'), and enumerates expected filing categories like accounts, confirmation statements, and charges. It is clear on its face, though it does not explicitly contrast itself with sibling tools such as list_officers or list_charges.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives useful in-tool guidance: 'Use `category` rather than paging through everything.' It also warns that document contents are not returned, setting an expectation about what not to use this for. However, it never names sibling alternatives or states when to prefer this tool over list_officers, list_charges, or related tools.

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

Deploy Server