Skip to main content
Glama

Uk Gazette

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Gazette Search Notices

gazette_search_notices
Read-onlyIdempotent

Search The Gazette — the UK's official public record of statutory notices (London, Edinburgh and Belfast editions, archive back to 1665). Full-text search plus filters for notice category, publication date range, edition, and location. Covers company events (liquidations, administrations, winding-up petitions, name changes), personal insolvency, deceased estates, road/planning orders, honours, state and royal notices. Use for "official UK notices about X", "gazette notices for company Y", "road closure orders near Z". Example: gazette_search_notices({ query: "Tesco", category: "corporate insolvency" })

Input Schema

NameRequiredDescriptionDefault
pageNoResults page, starting at 1
sortNo"newest" (default) or "oldest"
limitNoResults per page, 1-50 (default 10)
queryNoFull-text search — company name, person, place, or any words appearing in the notice text
editionNoRestrict to one edition: "london", "edinburgh", or "belfast"
categoryNoNotice category — a name like "corporate insolvency", "wills & probate", "road restrictions", or a code from gazette_notice_categories (G-code or legacy 2-digit)
locationNoUK postcode or town/city name to search around (needs distance_miles, default 5)
notice_typesNoAdvanced: one or more 4-digit notice type codes joined with "+", e.g. "2450" (petitions to wind up)
distance_milesNoRadius in miles around location (default 5)
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: +[
+  {
+    "category": "corporate insolvency",
+    "query": "Tesco"
+  },
+  {
+    "distance_miles": 10,
+    "limit": 20,
+    "location": "Manchester",
+    "published_after": "2024-01-01",
+    "query": "road closure"
+  }
+]
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations indicate the tool is read-only, idempotent, and non-destructive. The description adds behavioral details about full-text search, filters, and the scope of notices covered, which goes beyond the annotations without contradicting them.

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?

The description is a single, concise paragraph that front-loads the main purpose and efficiently covers key features, examples, and usage suggestions without unnecessary words.

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 search tool with 11 parameters and no output schema, the description adequately covers the input purpose and parameters. It could be improved by briefly describing the expected output format, but overall it provides sufficient context for an AI agent.

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%, so the description does not need to repeat parameter details. It adds value by providing an example call and explaining the category types, but this is minimal additional semantic context.

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 the tool searches The Gazette, the UK's official public record of statutory notices, covering multiple editions and a wide range of notice types. It distinguishes itself from sibling tools like gazette_deceased_estates and gazette_insolvency_notices by being a general search tool.

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 provides specific use cases such as 'official UK notices about X' and 'gazette notices for company Y', and gives an example query. However, it does not explicitly state when not to use this tool versus its more specialized siblings.

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
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources