UK Due Diligence

Overview Schema Source Related Servers Discussions Admin

Get Company Profile

company_profile

Read-onlyIdempotent

Fetch a UK company's Companies House profile by company number to check status, address, SIC codes, filing compliance, and outstanding charges. Use company_search first to find the number.

Instructions

Fetch the full Companies House profile for a company number.

Returns status, registered address, SIC codes, filing compliance (overdue accounts and confirmation statement flags), and whether the company has outstanding charges. Use company_search first to find the company number.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`company_number`	Yes	Companies House company number (8 digits, e.g. '03782379'). Returned by company_search.

Output Schema

TableJSON Schema

Name	Required	Description
`accounts`	No	Accounts filing status and due dates.
`sic_codes`	No	Standard Industrial Classification codes.
`has_charges`	No	True if the company has at least one outstanding or part-satisfied charge (secured debt) — not yet fully discharged. False if every charge on record is fully satisfied, or there are none. Null if the charges check could not be completed, or if a charge was returned with an unrecognized status that can't be confidently classified. Use company_charges for the full charge-by-charge detail.
`company_name`	No	Registered company name.
`company_type`	No	Companies House company type code.
`company_number`	Yes	Companies House company number.
`company_status`	No	Current status (active, dissolved, in liquidation, etc.).
`date_of_creation`	No	Incorporation date (ISO YYYY-MM-DD).
`confirmation_statement`	No	Confirmation statement filing status and next due date.
`registered_office_address`	No	Registered office address as returned by Companies House.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv1.3.0Aug 28, 2026

addedOutput schema / properties / has_charges / anyOf

Added value: +[
+  {
+    "type": "boolean"
+  },
+  {
+    "type": "null"
+  }
+]

changedOutput schema / properties / has_charges / default
```
Previous value: -falseNew value: +null
```

changedOutput schema / properties / has_charges / description

Previous value: -"True if the company has outstanding registered charges (secured debt), derived from the /charges endpoint. A due diligence signal."New value: +"True if the company has at least one outstanding or part-satisfied charge (secured debt) — not yet fully discharged. False if every charge on record is fully satisfied, or there are none. Null if the charges check could not be completed, or if a charge was returned with an unrecognized status that can't be confidently classified. Use company_charges for the full charge-by-charge detail."

removedOutput schema / properties / has_charges / type
```
Removed value: -"boolean"
```

Addedv1.0.6May 2, 2026
Removedv1.0.1May 1, 2026
First observedv1.0.0Apr 29, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already cover readOnly, openWorld, idempotent, and non-destructive behavior. The description adds useful behavioral context by specifying what the profile includes, such as overdue accounts, confirmation statement flags, and outstanding charges. No contradiction exists between the description and 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?

Three compact sentences: purpose, return contents, and prerequisite workflow. Every sentence adds value, and the most important information is front-loaded. No filler or redundant restatement of the tool name.

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?

The single parameter is fully documented in the schema, output schema exists so return values are defined elsewhere, annotations cover the safety profile, and the description provides scope and a prerequisite. Nothing critical is missing for an agent to invoke the tool correctly.

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?

The input schema already documents company_number with length constraints, format example, and a pointer to company_search. The description reinforces that the tool is called with a company number but adds little beyond what the schema provides. With 100% schema coverage, the baseline of 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 states a specific verb and resource: 'Fetch the full Companies House profile for a company number.' It also lists the returned data (status, registered address, SIC codes, filing compliance, outstanding charges), which clearly distinguishes it from sibling tools like company_search, company_officers, and company_psc.

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 workflow guidance: 'Use company_search first to find the company number.' This is clear and actionable, though it doesn't explicitly state when not to use this tool in favor of other siblings like company_officers or company_charges.

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

Deploy Server