A
licenseNot graded
qualityB
maintenanceEnables 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
government-tenders
Server Details
Search government tenders and public procurement opportunities with structured results.
If you are the author of this connector, you can claim ownership with GitHub, an HTTP challenge, or a DNS record. 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
- Repository
- DataLeadsPRO/government-tenders
- GitHub Stars
- 0
- Server Listing
- government-tenders
TDQS
D1.7/5.0
Scored across 1 tool
Disambiguation5/5
With only one tool available, there is no possibility of confusing it with another tool. The purpose of tenders_search is clear and unambiguous.
Naming Consistency3/5
The single tool name 'tenders_search' is readable and follows a noun_verb style, but there is no other tool to establish a predictable pattern. Consistency cannot be meaningfully assessed with only one name.
Tool Count2/5
A government tenders server with only one tool feels significantly under-scoped. The domain typically requires at least search, detail retrieval, and status/filter operations, so one tool is too few for the apparent purpose.
Completeness2/5
Only search is exposed, leaving obvious gaps such as retrieving a specific tender, listing tenders by status, or getting full tender details. Agents can discover tenders but have no way to perform follow-up operations beyond the initial search.
Available Tools
1 tooltenders_searchDInspect
V1 Tenders Search
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| query | No | ||
| region | No | ||
| maxTimeout | No |
TDQS
D1.1/5.0
Behavior1/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It does not mention whether results are returned, whether the operation is read-only, any rate limits, timeouts, authentication requirements, or possible side effects. The only implied behavior is 'search', which is already in the name.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness2/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is short, but this is under-specification rather than effective conciseness. 'V1 Tenders Search' adds no actionable information and does not earn its place; there is no front-loaded useful content.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness1/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given multiple undocumented parameters, no output schema, no annotations, and a vague description, the tool definition is far too incomplete for an agent to select and use reliably. Critical context about expected inputs and outputs is entirely absent.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters1/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, and the description does not explain any of the four parameters: limit, query, region, and maxTimeout. The description must compensate for the schema gap but provides no parameter-level meaning, defaults, formats, or usage hints.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose1/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description 'V1 Tenders Search' simply restates the tool name 'tenders_search' with a version prefix. It identifies no specific verb, resource, or scope beyond what the name already conveys, and it does nothing to distinguish the tool from any other search behavior.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines1/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no guidance about when to use this tool, what query or region values are appropriate, or how it relates to alternatives. No sibling tools are listed, but the description still fails to provide any context for invocation decisions.
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
Search EU public tenders across TED and 8 national portals. Monitor, match, and analyse procurement.
- GovTribeOAuthcom.govtribe
Search U.S. federal, state, and local government procurement data and intelligence.
Government tender search for AI agents. UK, EU and US procurement opportunities.
Search public procurement notices from 17 sources across Germany, the EU and the UK. Read-only.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables search and analysis of European public procurement tenders, including EU above-threshold (TED) and below-threshold from 11 national sources, with hybrid search and filtering.MIT
- AlicenseNot gradedqualityCmaintenanceEnables querying international public procurement data, including government tenders, through the Open Contracting standard.1 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables searching and analyzing Indian government tenders from multiple portals (CPPP, eProc Rajasthan, Defence) via natural language queries, returning OCDS-compliant data.2MIT
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.