Skip to main content
Glama
kaylum54

companies-house-screening-mcp

by kaylum54

Get filing history

get_filing_history
Read-onlyIdempotent

Retrieve filing history from Companies House to verify on-time submissions, review account reference dates, or track a competitor's filing pattern. Filter by category to reduce volume.

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
NameRequiredDescriptionDefault
verboseNoAlso 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.
categoryNoRestrict to one category, e.g. accounts, confirmation-statement, officers, mortgage, address, capital, incorporation, resolution, insolvency.
start_indexNoZero-based offset into the full result set. Use pagination.has_more to decide.
company_numberYesEight-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_pageNoHow many records to return. Defaults to the API default; the maximum is 100.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
rawNoThe untouched Companies House payload. Present only when verbose was true.
metaYesProvenance and budget for this answer.
filingsYes
paginationYesWhere this page sits in the full result set.
company_numberYes
Install Server

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare read-only, open-world, and idempotent behavior, so the safety profile is covered. The description adds valuable behavioral context not in annotations: returned descriptions are Companies House template keys, not translated, with an explanation of why partial translation would be misleading. This helps the agent set correct expectations about the output format.

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 front-loaded with the core purpose and use cases, then covers the important template-key nuance and filtering. It is a bit longer than strictly necessary, but every sentence contributes useful information and none is redundant filler.

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 a complete input schema, an output schema, and informative annotations, the description is sufficient for an agent to select and invoke the tool correctly. It covers purpose, use cases, a key output-format behavior, and the essential prerequisite (company number); remaining details like pagination are already structured in the schema.

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 schema fully documents all five parameters. The description adds only marginal semantic value by mentioning `category` filtering and the company-number requirement, but the heavy lifting is already done by the input schema. Baseline 3 is appropriate.

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 (accounts, confirmation statements, officer changes, mortgages, address changes). This clearly distinguishes it from sibling tools like get_company or get_officers, which cover different aspects of company data.

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 gives explicit use cases — judging filing timeliness, checking last accounts made up, watching a competitor's cadence — and advises using `category` to cut volume. It does not name alternative tools or state when not to use this tool, but the use-case framing is strong enough that an agent can infer appropriate selection.

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

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/kaylum54/companies-house-screening-mcp'

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