Skip to main content
Glama

Gazette Insolvency Notices

gazette_insolvency_notices
Read-onlyIdempotent

Search official UK insolvency notices in The Gazette, the statutory public record where liquidations, administrations, winding-up petitions and orders, bankruptcy orders, creditors' meetings, and notices to creditors MUST be published. The go-to source for "is UK company X in liquidation/administration", monitoring company distress, or tracking personal bankruptcies. Search by company name or Companies House number (both are indexed). scope narrows to "corporate" or "personal" insolvency. Example: gazette_insolvency_notices({ company: "Wilko", scope: "corporate" })

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "scope": "corporate",
      "company": "Wilko"
    },
    "name": "gazette_insolvency_notices"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoResults page, starting at 1
limitNoResults per page, 1-50 (default 10)
scopeNo"corporate" (default), "personal", or "all"
companyNoCompany name, Companies House number, or person name to search
notice_typesNoAdvanced: 4-digit notice type codes joined with "+", e.g. "2450" petitions to wind up
published_afterNoEarliest publication date, YYYY-MM-DD
published_beforeNoLatest publication date, YYYY-MM-DD

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "company": "Wilko",
      +    "scope": "corporate"
      +  },
      +  {
      +    "company": "05474837",
      +    "published_after": "2023-01-01",
      +    "scope": "corporate"
      +  }
      +]
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds domain-meaningful context beyond that: these are statutory publications that MUST appear, both company name and Companies House number are indexed, and scope partitions results into corporate/personal. Pagination behavior and result-field detail are left to the schema or unstated.

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 purpose and the use-case triggers are front-loaded, followed by search-key guidance and a worked example, which is a sensible order. It is somewhat dense with capitalized emphasis ('MUST') and a duplicated example already present in the schema, but no sentence is genuinely wasted.

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?

For a 7-parameter, all-optional search tool with a fully documented schema and read-only annotations, the description covers the corpus, the searchable keys, and the scoping dimension adequately. The main residual gap is that no output schema exists, so the shape of returned notices is never described.

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 every parameter is already documented in the input schema, which sets the baseline at 3. The description reinforces that both company names and Companies House numbers are indexed and explains scope's corporate/personal split, but this largely restates the schema rather than adding new semantics such as date format constraints or notice_types coding.

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?

States a specific verb and resource: 'Search official UK insolvency notices in The Gazette, the statutory public record', and enumerates the notice categories it covers (liquidations, administrations, winding-up petitions, bankruptcy orders). An agent knows exactly what corpus this queries. It does not, however, differentiate itself from the sibling gazette_search_notices, which by name appears to be a close overlap, so it falls short of a 5.

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?

Gives concrete triggering questions — 'is UK company X in liquidation/administration', monitoring company distress, or tracking personal bankruptcies — which is strong when-to-use guidance. It offers no explicit when-not guidance and does not route the agent to a specific alternative for generic notice searching, so it stops at 4.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.