UK Business Tools - Ledgerhall

Search GOV.UK

gov_govuk_search

Read-onlyIdempotent

Search GOV.UK's 700k+ content items using the official Search API.

Returns a list of matching content items with title, description, link, format, owning organisation(s), and last updated timestamp.

Use filter_format to narrow to specific content types (e.g. 'transaction' for citizen-facing services, 'guide' for guidance, 'publication' for official documents). Use filter_organisations to restrict to a department.

Input Schema

TableJSON Schema

Name	Required	Description
`count`	No	Number of results to return (1–50)
`order`	No	Sort order. Use '-public_timestamp' for newest-first (default relevance).
`query`	Yes	Free-text search query, e.g. 'universal credit eligibility' or 'MOT check'
`start`	No	Offset for pagination, e.g. 10 for the second page of 10 results
`filter_format`	No	Filter by document format. Common values: 'guide', 'answer', 'transaction', 'publication', 'news_article', 'detailed_guide', 'hmrc_manual_section', 'travel_advice', 'organisation'. Leave blank to search all types.
`filter_organisations`	No	Filter by organisation slug, e.g. 'hm-revenue-customs', 'department-for-work-pensions', 'driver-and-vehicle-standards-agency'.

Output Schema

TableJSON Schema

Name	Required	Description
`count`	Yes	Max results requested for this page.
`query`	Yes	The free-text query that was searched.
`start`	Yes	Offset used for this page (zero-based).
`total`	Yes	Total matching results across all pages on GOV.UK.
`results`	No	Matching pages. Use the `link` field of any result as the `base_path` input to govuk_get_content for the full item.
`has_more`	Yes	True if more results exist beyond this page. Re-call with start=start+returned to fetch the next page.
`returned`	Yes	Number of results actually returned in this response.

TDQS

A4.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds beneficial context (returns list with specific fields, official API) but does not disclose rate limits, authentication needs, or pagination behavior beyond the schema's start parameter. 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is three concise sentences: first states purpose and source, second summarizes return fields, third gives filtering guidance. Every sentence earns its place, and the key verb 'Search' is front-loaded.

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?

Given the output schema and annotations, the description sufficiently covers purpose, return shape, and filter usage. It lacks explicit guidance on when to use this tool versus sibling tools, but that is addressed in the usage dimension and does not significantly hinder completeness for a search tool.

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?

Schema description coverage is 100%, so baseline is 3. The description enriches parameter semantics by providing concrete examples for filter_format (transaction, guide, publication) and filter_organisations (with departmental slugs), which is not present in 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 clearly states the action (search), resource (GOV.UK content items), and method (official Search API). It also distinguishes itself from siblings like gov_govuk_get_content (retrieval of specific items) and gov_govuk_grep_content (grep-style search) by emphasizing the API-based search over the broader content set.

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 clear usage context, noting how to narrow with filter_format and filter_organisations, including practical examples for content types. It does not explicitly name alternative tools or exclusion criteria, so it stops short of a 5.

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

All UK Business Tools - Ledgerhall tools Inspect

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

A4/5.0

Disambiguation4/5

Tools are well-grouped by domain prefixes (dd_, gov_, law_, prop_) with clear descriptions that differentiate them. However, there is minor overlap, e.g., dd_search could be used instead of individual searches, and dd_fetch versus dedicated profile tools might cause confusion.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern with domain-specific prefixes (dd_, gov_, law_, prop_). Names are descriptive and predictable, e.g., dd_charity_search, gov_govuk_search, law_bills_search_bills.

Tool Count4/5

70 tools is high but justified by the broad scope covering due diligence, government, legal, and property domains. Each domain has a reasonable number of tools (about 15-20 each). The count is on the upper end but still manageable.

Completeness5/5

The tool set is comprehensive across all domains: full CRUD for companies and charities, detailed legal research (cases, legislation, parliament, citations), property data (EPC, planning, price paid, rentals), and government information. No obvious gaps for the intended use cases.

Resources

Need Help?