Skip to main content
Glama

Gov Uk Content Search

gov_uk_content_search
Read-onlyIdempotent

Search everything published on GOV.UK, guidance, forms, statistics, consultations, news, policy papers and departmental manuals, by free text, optionally narrowed to one document format. Returns titles, URL paths and publication timestamps.

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": {
      "query": "driving license"
    },
    "name": "gov_uk_content_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
countNo
queryYes
startNo
filter_formatNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, openWorld, idempotent and non-destructive behavior, so the safety profile is covered. The description adds the breadth of the corpus and names the returned fields, but says nothing about result limits, pagination behavior, or ranking/ordering — and the return-field listing duplicates the existing output schema.

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?

Two sentences, front-loaded with the core verb and scope, with the filtering and return information following logically. The document-type enumeration is somewhat long but earns its place by defining corpus coverage.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The output schema covers return values, so the description needn't detail them. But with zero schema coverage on four parameters, the absence of any pagination or format-value guidance leaves a real gap for an agent trying to page through results or filter correctly.

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

Parameters2/5

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

Schema description coverage is 0% for all four parameters, so the description carries the full burden. It clarifies 'query' (free text) and gestures at 'filter_format' (one document format) but says nothing about 'count' or 'start', leaving pagination semantics entirely undocumented, and gives no hint of accepted format values.

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 ('Search') and resource ('everything published on GOV.UK') and enumerates the content types covered (guidance, forms, statistics, consultations, news, policy papers, departmental manuals), which gives an agent a clear picture of scope. It does not explicitly differentiate itself from overlapping siblings such as hmrc_manual_search or content, so it stops 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'by free text, optionally narrowed to one document format' implies how to use the tool, and the scope statement implies when it applies. However, there is no explicit when-to-use/when-not guidance and no mention of when a more targeted sibling (e.g. hmrc_manual_search for HMRC manuals) would be preferable, despite 'departmental manuals' being claimed here too.

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.