UK Business Tools - Ledgerhall

Overview Schema Source Related Servers Discussions Admin

Search Gazette Corporate Insolvency Notices

dd_gazette_insolvency

Read-onlyIdempotent

Find official UK insolvency notices for any company or person. Search the Gazette's index by name, filter by date or notice type, and access full legal wording from the result's notice ID.

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.

First observedv0.2.1Sep 21, 2026

TDQS

A4.2/5.0

Behavior4/5

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

It discloses behavioral details beyond the read-only/idempotent annotations: internal DD severity sorting, the fact that the notice label is a source fact, the legal effectiveness of Gazette notices, and the notice_numeric_id trail. These are substantive additions that go beyond simply saying it is read-only.

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 core purpose is front-loaded in the first sentence, with follow-up and legal context in compact paragraphs. A small amount of redundancy exists between the opening phrase and the second sentence, but the organization is clean.

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 description, combined with the rich annotations and output schema, gives an agent enough to correctly invoke the tool and understand the result: legal significance, sorting behavior, result identifier, and how to get the full notice. Nothing critical is 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?

Schema coverage is 100% with all parameters described, so the schema does the heavy lifting. The description adds only minor context such as 'authoritative Gazette notice-code taxonomy' and does not meaningfully explain aliases or extended date semantics 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 the exact operation and resource: searching The Gazette's corporate-insolvency notice index by entity. It clearly distinguishes this from generic gazette or company searches by referencing the Gazette notice-code taxonomy and the notice:// result 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 explains when the tool is appropriate—searching the official Gazette insolvency record—and provides a concrete follow-up: use notice://{notice_numeric_id} for full legal wording. It stops short of explicitly naming when to use or not use sibling alternatives like dd_gazette_notice.

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

Deploy Server