Skip to main content
Glama
uk-tenders-mcp

uk-tenders-mcp

by atz1man

search_tenders

Read-only

Search open UK public-sector tenders from Find a Tender and Contracts Finder, filter by keywords or regions, remove expired or duplicate notices, and return soonest deadlines with source links.

Instructions

Find open UK public-sector tenders published or updated in the last days days (1-30).

Searches Find a Tender and Contracts Finder together, removes notices listed on both, and drops tenders whose deadline has passed. Optional filters: keywords (any match in title or description) and regions (for example ["London", "South East"]). Returns at most limit (1-50), soonest deadline first, each with buyer, value, deadline, days_left and a source_url to cite.

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": "search_tenders"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNo
limitNo
sourceNoall
regionsNo
keywordsNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, and the description adds real behavior: it queries Find a Tender and Contracts Finder together, de-duplicates notices listed on both, drops expired tenders, and returns results soonest-deadline-first. The main omission is that the `source` parameter can narrow to a single registry, which contradicts the flat claim that it always searches both.

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?

Three compact sentences, front-loaded with scope, then filters, then return shape — no filler. The closing clause listing returned fields is mildly redundant given an output schema exists, but it is short and orients the agent before the call.

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?

For a five-parameter read-only search with an output schema and safety annotations already in place, the description covers scope, filtering, de-duplication, expiry handling, ordering, and result caps. Only the `source` filter and default values are left unstated, which is a small gap relative to everything else it supplies.

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 0%, so the description must carry the load, and it does add value by supplying ranges the schema lacks (`days` 1-30, `limit` 1-50) and by giving a concrete regions example. However, it never explains the `source` enum (all/find_a_tender/contracts_finder) and does not mention that `days` defaults to 7 and `limit` to 20, leaving one of five parameters and all defaults undocumented.

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?

States a specific verb and resource ('Find open UK public-sector tenders') plus the freshness window and both underlying sources, so an agent knows exactly what corpus is being queried. It is unmistakably distinct from the sibling tools (list_profiles, get_company, score_tenders), which operate on different objects.

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?

Gives clear context for when this applies: open tenders only, published or updated within `days`, with expired deadlines dropped. It marks keywords and regions as optional filters, but never states when to prefer this over score_tenders or what to do if zero results come back.

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