UK Due Diligence

Overview Schema Source Related Servers Discussions Admin

Search Gazette Corporate Insolvency Notices

gazette_insolvency

Read-onlyIdempotent

Search The Gazette's official insolvency notice index by entity name to confirm if a UK company or person has a formally published insolvency event for due diligence.

Instructions

Search The Gazette's insolvency notice index by entity name.

Searches The Gazette's corporate-insolvency notice index using the authoritative Gazette notice-code taxonomy. Results are sorted by an internal DD severity score; the notice label itself remains a source fact.

Each result includes a notice_numeric_id. Read the full legal wording via the notice://{notice_numeric_id} resource.

The Gazette is the official UK public record. A notice here means the event has been formally published and is legally effective.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	No	Company or individual name to search for in Gazette insolvency notices
`query`	No	Alias for name.
`end_date`	No	Filter notices up to this date (YYYY-MM-DD)
`start_date`	No	Filter notices from this date (YYYY-MM-DD)
`entity_name`	No	Deprecated alias for name.
`max_notices`	No	Cap on notices returned, applied after severity/date sort. Default 20. The Gazette insolvency feed returns up to 100 results per search — raise to 100 to see the full set.
`notice_type`	No	Filter by Gazette notice code (e.g. '2450' petition to wind up a company, '2452' winding-up order, '2410' appointment of administrators). Omit to search all.

Output Schema

TableJSON Schema

Name	Required	Description
`notices`	No	Matching notices, sorted by severity (desc) then date (desc).
`end_date`	No	Upper bound of the date range filter, if any.
`start_date`	No	Lower bound of the date range filter, if any.
`entity_name`	Yes	Entity name that was searched.
`total_notices`	Yes	Total notices returned after deduplication, sorting, and cap.
`max_notices_cap`	Yes	The max_notices cap applied. Upstream may have more matching notices.
`notice_type_filter`	No	Notice code filter applied, or null if all codes searched.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv1.3.0Aug 28, 2026

changedInput schema / properties / notice_type / description

Previous value: -"Filter by notice code (e.g. '2441' winding-up petition, '2443' winding-up order, '2448' administration order, '2460' striking-off). Omit to search all."New value: +"Filter by Gazette notice code (e.g. '2450' petition to wind up a company, '2452' winding-up order, '2410' appointment of administrators). Omit to search all."

changedOutput schema / properties / notices / items / properties / notice_code / description

Previous value: -"Gazette notice code (e.g. '2443' winding-up order, '2448' administration order)."New value: +"Gazette notice code (e.g. '2450' petition to wind up a company, '2452' winding-up order for a company)."

changedOutput schema / properties / notices / items / properties / severity / description

Previous value: -"Internal severity score 0-10. Higher = more serious (10 = Winding-Up Order, 9 = Administration Order / Receiver, 0 = unclassified)."New value: +"Internal severity score 0-10. Higher = more serious (10 = winding-up order, 9 = administration/receiver/liquidator appointment, 0 = informational or unclassified)."

Changed9 schema fields changedv1.1.1Jul 29, 2026

addedInput schema / properties / entity_name / anyOf

Added value: +[
+  {
+    "maxLength": 200,
+    "minLength": 2,
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / entity_name / default
```
Added value: +null
```

changedInput schema / properties / entity_name / description

Previous value: -"Company or individual name to search for in Gazette insolvency notices"New value: +"Deprecated alias for name."

removedInput schema / properties / entity_name / maxLength
```
Removed value: -200
```
removedInput schema / properties / entity_name / minLength
```
Removed value: -2
```
removedInput schema / properties / entity_name / type
```
Removed value: -"string"
```

addedInput schema / properties / name

Added value: +{
+  "anyOf": [
+    {
+      "maxLength": 200,
+      "minLength": 2,
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Company or individual name to search for in Gazette insolvency notices"
+}

addedInput schema / properties / query

Added value: +{
+  "anyOf": [
+    {
+      "maxLength": 200,
+      "minLength": 2,
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Alias for name."
+}

removedInput schema / required
```
Removed value: -[
-  "entity_name"
-]
```

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

TDQS

A4.1/5.0

Behavior4/5

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

The description adds meaningful behavioral context beyond the annotations: results are sorted by an internal DD severity score, the notice label is preserved as a source fact, and a published notice is legally effective. These details are not visible in the annotations and help an agent interpret results and avoid assuming chronological ordering.

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 well-structured and mostly front-loaded, but the first two sentences both announce the same search operation with slightly different phrasing. Every other sentence earns its place by explaining sorting, result IDs, or the legal significance of a Gazette notice.

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?

The description covers the key non-obvious behaviors an agent needs: the insolvency-specific scope, severity-based sorting, the presence of notice_numeric_id, the separate notice resource for full wording, and the legal effectiveness of published notices. Given that an output schema exists and the parameter schema is fully documented, nothing critical appears missing.

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 provides 100% coverage of parameter meanings, including aliases, date formats, max_notices caps, and notice_type examples. The description adds some useful context around the notice-code taxonomy and the result's numeric ID, but it does not materially improve parameter-level understanding beyond 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?

The description names a specific verb ('Search') and a specific resource ('The Gazette's corporate-insolvency notice index'), and also indicates the search is by entity name. It differentiates this tool from siblings like gazette_notice by noting results contain a notice_numeric_id and that the full legal wording is available separately via a notice:// resource.

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 clearly frames this as the entry point for finding insolvency notices and then directs the user to read the full legal wording via notice://{notice_numeric_id}, which functions as an implicit alternative path. It does not explicitly state 'use gazette_notice for full notices' or list exclusions, but the context is clear enough for an agent to choose correctly.

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

Deploy Server