oro-intel-mcpofficial
A
licenseNot graded
qualityD
maintenanceUK public procurement data for AI agents. Tenders, contracts, buyer and supplier profiles over MCP and REST. 250 free credits.
MIT
UK Data: UK public tenders
Server Details
UK public sector tenders and contract awards from Find a Tender: values, buyers, winners, deadlines
If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- ChatGPT
- –
- Claude
- –
TDQS
A3.7/5.0
Scored across 1 tool
Disambiguation5/5
There is only one tool, so there is no possibility of confusing it with another operation. Its purpose (searching UK public tenders and contract awards) is unambiguous and clearly scoped.
Naming Consistency4/5
The single name 'tenders_search' is descriptive and snake_case, but it follows a noun_verb order rather than the more conventional verb_noun pattern (e.g. search_tenders). With only one tool there is no inconsistency to speak of, just a minor stylistic deviation.
Tool Count3/5
A one-tool server is at the thin end of the range for a data domain that spans two sources (Find a Tender and Contracts Finder) plus both tender and award stages. The single tool is feature-rich with many filters, but the surface overall feels minimal.
Completeness3/5
Search is well covered with keywords, stage, value range, buyer and date filters, but there is no way to fetch full detail for a specific tender/award by ID, no pagination or result-expansion operation, and no way to retrieve documents or contacts. These are notable gaps an agent would hit when it needs the specifics of a found notice.
Available Tools
1 tooltenders_searchAInspect
Search UK public sector tenders and contract awards from Find a Tender and Contracts Finder: keywords, stage (tender/award/both), value range, buyer, days back. (cost: 3 credits)
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | number 1-500 | |
| stage | No | tender|award|both | |
| sources | No | array of fts|cf | |
| daysBack | No | number 1-365 | |
| keywords | No | array of strings | |
| maxValue | No | number | |
| minValue | No | number | |
| buyerContains | No | string |
TDQS
A3.7/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden. It usefully discloses the cost ('3 credits'), which is real context an agent needs before calling, but says nothing about result volume, ordering, pagination, or whether an empty result set is possible for over-narrow filters.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
A single sentence front-loads the resource and scope, then lists the filter axes, with the cost callout appended in parentheses. Nothing is redundant and no sentence is wasted.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With 8 all-optional parameters, full schema coverage, and no output schema, the description covers enough for correct invocation. It omits default values (e.g. limit/daysBack defaults) and what a result record looks like, which would matter for a search tool returning structured listings.
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, but the description adds genuine meaning by expanding opaque schema tokens: 'fts|cf' is explained as Find a Tender vs Contracts Finder, and 'both' is clarified as the valid stage option. Value range and days-back are mapped to their purpose rather than restated as raw types.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose4/5
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource ('Search UK public sector tenders and contract awards') and names the underlying data sources (Find a Tender, Contracts Finder) plus the supported filter axes. It largely distinguishes itself from the closest sibling eu_tenders by the explicit 'UK public sector' scoping, but never names that alternative outright.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines3/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The enumerated filters ('keywords, stage, value range, buyer, days back') imply when the tool is appropriate, i.e. any keyword/date/value-scoped tender lookup. There is no explicit when-to-use vs eu_tenders guidance, no statement about combining filters, and no exclusions or prerequisites.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
1 tool update
- First observed
tenders_search
Related MCP Connectors
UK and Ireland public sector tenders, contract awards, buyers and expected re-tenders.
Public tenders and contract awards from EU TED and UK Find a Tender, with buyer, value and deadline.
UK public tenders and contract awards with winning suppliers, from Find a Tender. x402 USDC.
UK public procurement data for AI agents: tenders, contracts, buyer and supplier profiles.
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceEnables searching UK government procurement data — Contracts Finder notices and contracts (with supplier and value), plus high-value Find a Tender Service tenders — and retrieving full details for any single notice. Covers NHS trusts, councils, police, universities and central government departments.193 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables searching and analyzing government tenders, contract awards, and pre-tender pipelines from 21 official sources, with tools for tender search, award intelligence, and detailed notice retrieval.MIT
- AlicenseAqualityBmaintenanceEnables AI agents to find, score, and monitor government contract opportunities across UK, EU, and US with AI-powered relevance scoring.2103 npm1MIT
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.