SiteCheck Company Records

UK awarded public contracts from Contracts Finder: notice

gov_ukcontracts_tenders

Read-only

UK awarded public contracts from Contracts Finder (OCDS search, stage=award): notice ID, date, buyer, contract title, awarded supplier and award value in GBP. Award notices only; the newest page of results. Takes about 15 s; allow a 45 s timeout. Related tools on this server, for a different need: gov_uk_gov_tenders when you need latest UK public sector tender notices from Find a Tender; gov_canadabuys_tenders when you need Open Government of Canada tender notices. Price: $0.002 in USDC per successful call, paid with x402 (Base, Solana or Arc); failed calls are not charged.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "gov_ukcontracts_tenders"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	Notices to return, 1 to 10 (default 5)

Output Schema

Name	Required	Description	Default
`awards`	No
`source`	No
`checkedAt`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Beyond the readOnly/openWorld annotations, the description discloses that only the newest page is available (no historical or paginated access), that a call takes about 15 s and should be given a 45 s timeout, and the exact cost model ($0.002 USDC per successful call via x402, failed calls free). These are exactly the non-obvious operational facts an agent needs before invoking.

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?

Dense but front-loaded: purpose and field list come first, then scope, then latency, then sibling routing, then pricing. Every element is relevant, though the pricing and latency clauses make it longer than strictly necessary for tool selection.

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?

Return fields are enumerated, latency and timeout are given, cost is stated, and sibling alternatives are named; with an output schema also present, 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.

Parameters3/5

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

Schema coverage is 100% and the single 'limit' parameter already documents its range (1-10, default 5), so the description adds no parameter meaning. Baseline 3 is appropriate since the schema carries the full burden here.

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 verb and resource ('UK awarded public contracts from Contracts Finder', OCDS stage=award) and enumerates the returned fields (notice ID, date, buyer, contract title, supplier, award value in GBP), which lets an agent distinguish it from the tender-notice siblings.

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 scopes usage explicitly ('Award notices only; the newest page of results') and routes the agent to two named alternatives with the condition that selects each (Find a Tender for latest tender notices, CanadaBuys for Canadian notices). It does not state an explicit when-not-to-use condition for this tool itself, so it falls 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 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?