Skip to main content
Glama

Uk Contracts

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Find A Tender Recent

find_a_tender_recent
Read-onlyIdempotent

Recent HIGH-VALUE UK government tenders and contract awards from the Find a Tender Service (find-tender.service.gov.uk) — the UK's above-threshold procurement portal (the post-Brexit replacement for EU TED, for larger public contracts). Use for "high value UK tenders", "above threshold UK government contracts", "Find a Tender notices", "large UK public sector contract opportunities". Returns recent notices newest-first. An optional keyword is matched over title, description, award title and AWARDED SUPPLIER — client-side, because the FTS API has no text search (it rejects a keyword parameter outright, allowing only stages/limit/cursor/updatedFrom/updatedTo). ALWAYS READ window_complete: false means the walk stopped at the page cap with more feed left, so a zero means "absent from the notices examined", not "not published" — narrow days until it is true. For a proper full-corpus keyword SEARCH of UK procurement, and for lower-value notices, use search_notices (Contracts Finder), which does have a real server-side index. Keyless.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
daysNoHow many days back to scan, 1–30. Default 7 when listing, 30 when a keyword is given (the 7-day feed is only ~30 notices, too few for a keyword to match).
limitNoMax notices to return, 1–100 (default 20).
stageNoNotice stage: "tender" (open opportunities, default), "award" (results), or "planning".
keywordNoOptional keyword to filter recent notices by title/description, e.g. "cloud", "construction". Omit to list all recent.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / days / description
      Previous value: -"How many days back to scan, 1–30 (default 7)."New value: +"How many days back to scan, 1–30. Default 7 when listing, 30 when a keyword is given (the 7-day feed is only ~30 notices, too few for a keyword to match)."
  2. Changed1 schema field changed
    • changedInput schema / examples
      Previous value: -[
-  {
-    "days": 7,
-    "limit": 20,
-    "stage": "tender"
-  },
-  {
-    "days": 14,
-    "keyword": "construction",
-    "limit": 30,
-    "stage": "award"
-  }
-]New value: +[
+  {
+    "days": 7,
+    "limit": 20,
+    "stage": "tender"
+  },
+  {
+    "days": 30,
+    "keyword": "MRI",
+    "stage": "tender"
+  },
+  {
+    "days": 3,
+    "keyword": "MRI",
+    "stage": "award"
+  }
+]
  3. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "days": 7,
+    "limit": 20,
+    "stage": "tender"
+  },
+  {
+    "days": 14,
+    "keyword": "construction",
+    "limit": 30,
+    "stage": "award"
+  }
+]
  4. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare read-only/idempotent/non-destructive/open-world, so the bar is lower, yet the description adds substantial context they cannot: keyword matching is client-side because the FTS API rejects a keyword parameter outright, and the `window_complete=false` flag means a zero result is "absent from notices examined" rather than "not published". It also notes the tool is keyless. These are exactly the operational caveats an agent needs to interpret results correctly.

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?

Front-loaded with purpose, then trigger phrases, then return ordering, then the two critical constraints, ending with the sibling handoff. Every sentence carries information, though the heavy parenthetical nesting (API parameter list, portal history) makes it denser than it needs to be for skimming.

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?

No output schema exists, and the description covers what an agent must know about returns: notices come newest-first and `window_complete` must be checked to interpret an empty result. Combined with the 100%-documented input schema, nothing needed to call or read this tool 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 baseline is 3, and the description genuinely adds beyond it: `keyword` is matched over title, description, award title and AWARDED SUPPLIER, which the schema does not state, and it explains why the default `days` changes when a keyword is supplied. It does not restate the numeric ranges already documented 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?

Names a specific verb+resource (recent UK government tenders/contract awards from Find a Tender Service) and states the scope precisely: above-threshold, post-Brexit replacement for EU TED. It explicitly separates itself from sibling search_notices/Contracts Finder for lower-value notices, so an agent can route without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Gives concrete trigger phrases ("high value UK tenders", "above threshold UK government contracts") and an explicit when-not plus alternative: "For a proper full-corpus keyword SEARCH of UK procurement, and for lower-value notices, use search_notices". This is exactly the when/when-not/alternative structure the top tier requires.

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

All Uk Contracts toolsInspect
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