SiteCheck Company Records

Search the Data.gov catalog: title, publisher

gov_data_gov

Read-only

Search the Data.gov catalog (300,000+ US federal, state and local open datasets): title, publisher and organisation, description, keywords, themes, access level, last modified and issued dates, whether a download exists, and each distribution (title, format/media type, download or access URL), plus the dataset page URL. Results come in relevance order; pass the returned next cursor to get the following page. Related tools on this server, for a different need: gov_clinicaltrials when you need ClinicalTrials.gov studies matching a condition, drug; gov_data_gov_uk when you need UK government open datasets from the data.gov.uk catalogue. 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"
  }
}

Input Schema

Name	Required	Description
`q`	Yes	Search words, e.g. water quality, crime, census tracts (required)
`after`	No	Cursor from a previous answer's next field, for the next page
`limit`	No	Datasets per page, 1 to 50 (default 20)

Output Schema

Name	Required	Description	Default
`q`	No
`next`	No
`count`	No
`source`	No
`datasets`	No
`checkedAt`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Goes well beyond the readOnlyHint/openWorldHint annotations by disclosing relevance ordering, cursor-based pagination ('pass the returned next cursor to get the following page'), and the payment model with price, currencies, and the fact that failed calls are not charged. Cost and pagination are exactly the operational facts an agent cannot infer from structured fields.

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?

One dense, front-loaded paragraph; purpose leads, alternatives and pricing follow. The long field enumeration is justified for relevance judgement, though the pricing/alternative-tool sentence could be split out for scanability.

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?

The tool has three params, full schema coverage, an output schema, and read/write annotations, so the description only needed to add ordering, pagination linkage, cost, and alternative routing - and it does all four. Nothing an agent needs to call this correctly is missing.

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 coverage is 100%, so the baseline is 3, but the description adds meaning the schema does not: 'after' is explicitly the value returned in the response's next field, which is the key coupling between calls. It adds nothing about q syntax or the limit ceiling beyond what the schema states, so it is not a 5.

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?

Names a specific verb and resource ('Search the Data.gov catalog') and scopes it with '300,000+ US federal, state and local open datasets'. The enumerated coverage (title, publisher, description, keywords, themes, access level, dates, distributions) tells an agent exactly what can be matched, which separates it from the sibling open-data catalogues.

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?

Explicitly routes two alternative needs away from this tool: gov_clinicaltrials for condition/drug studies and gov_data_gov_uk for UK datasets. That is real when-to-use-else guidance, but it is limited to two of the many sibling catalogues and gives no guidance on query formulation or when this catalogue would be the wrong choice for non-US data generally.

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?