SiteCheck Company Records

UK government open datasets from the data.gov.uk catalogue

gov_data_gov_uk

Read-only

UK government open datasets from the data.gov.uk catalogue (CKAN API): title, publisher, licence, last modified date, number of resources and dataset link, for a search term. Catalogue metadata only, not the data files themselves. Related tools on this server, for a different need: gov_governmentbids when you need open US/Canadian government bid solicitations listed; gov_govdeals when you need live US government surplus auctions on GovDeals. Price: $0.002 in USDC per successful call, paid with x402 (Base, Solana or Arc); failed calls are not charged.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "q": "<q>"
    },
    "name": "gov_data_gov_uk"
  }
}

Input Schema

Name	Required	Description	Default
`q`	Yes	Search text, 2 to 80 characters
`rows`	No	Datasets to return, 1 to 10 (default 5)

Output Schema

Name	Required	Description	Default
`query`	No
`source`	No
`datasets`	No
`checkedAt`	No
`totalDatasets`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already cover safety (readOnlyHint) and reach (openWorldHint), but the description adds genuinely new operational facts: the paid model at $0.002 USDC per successful call via x402 on Base, Solana or Arc, and that failed calls incur no charge. That billing detail materially affects invocation decisions. It does not cover rate limits or pagination depth, which keeps it below 5.

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?

It is front-loaded: purpose and returned fields come first, then the metadata caveat, then siblings, then pricing. Every clause is informative, though the two-sibling routing sentence is somewhat long for a marginal steering benefit.

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?

An output schema exists, so return values need not be explained, yet the description still previews the field set. Combined with the price, the metadata-only caveat, and the readOnly annotation, an agent has everything needed to decide and call correctly.

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%, with 'q' (2-80 chars) and 'rows' (1-10, default 5) fully documented in the schema. The description adds no further meaning about search syntax, matching behaviour, or whether 'q' supports fielded queries, so the baseline of 3 applies.

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 names a specific resource (UK government open datasets from the data.gov.uk catalogue via the CKAN API) and enumerates the returned fields (title, publisher, licence, last modified, resource count, dataset link). It also bounds the scope explicitly: catalogue metadata only, not the data files themselves.

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?

It states the calling context ('for a search term') and an explicit exclusion ('Catalogue metadata only, not the data files themselves'), which prevents an agent from expecting download links to actual data. The related-tools sentence routes to gov_governmentbids and gov_govdeals, though those are different needs rather than substitutes for this tool; it does not disambiguate against similar open-data siblings such as gov_data_gov or gov_australia_data_gov_au.

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

All SiteCheck Company Records tools Inspect

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

Need Help?