Skip to main content
Glama

Uk Gazette

by io.github.pipeworx-io

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" })

Input Schema

TableJSON 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

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already provide readOnlyHint, openWorldHint, idempotentHint, destructiveHint. The description adds context about the statutory nature of the data and indexing, but does not add behavioral traits beyond what annotations provide. No contradiction.

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?

Three sentences plus an example, all front-loaded with the most critical information. No unnecessary words. The example helps illustrate usage. Efficient and clear.

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 7 parameters with full schema descriptions and comprehensive annotations, the description covers use cases, example, and search strategies. No output schema exists, but the rules state description needn't explain return values. Complete for effective agent usage.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

All 7 parameters are documented in the schema. The description adds value by explaining that 'company' accepts both names and Companies House numbers (both indexed), and that 'scope' narrows to corporate or personal insolvency, enhancing the schema descriptions.

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 clearly states it searches official UK insolvency notices in The Gazette, listing specific notice types and providing example usage. It distinguishes from sibling tools like gazette_deceased_estates and gazette_get_notice by its specific focus on insolvency.

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?

Provides explicit use cases ('go-to source for checking company liquidation/administration, monitoring distress, tracking personal bankruptcies') and search strategies (by name or Companies House number). Lacks explicit when-not-to-use guidance but implies context through scope parameter.

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

All Uk Gazette toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.5/5.0
Disambiguation2/5

Many tools have overlapping purposes (e.g., ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded all serve similar query routing). Tools from unrelated domains (UK Gazette, Polymarket betting, AI visibility checks) are mixed together, making it hard for an agent to distinguish which tool to use for a given task.

Naming Consistency1/5

Naming is chaotic: some tools use descriptive phrases with underscores (gazette_deceased_estates, polymarket_arbitrage), others use generic verbs (remember, recall, forget), and some include version or mode indicators (ask_pipeworx_beta, scan_competitor_ai_presence). No consistent pattern across the set.

Tool Count2/5

With 36 tools, the server is overstuffed for its purported focus on the UK Gazette. The majority of tools (Polymarket, Pipeworx general, AI visibility, etc.) are unrelated to the server's name, making it feel like a bundling of many services into one, which is excessive for a coherent tool set.

Completeness2/5

For a server named 'Uk Gazette', there are only a handful of Gazette-specific tools (gazette_search_notices, gazette_insolvency_notices, etc.), while the rest cover unrelated domains. This leaves obvious gaps for Gazette-related tasks (e.g., no tool for searching particular notice types or filtering by edition), despite the large tool count.

Resources