A
licenseNot graded
qualityD
maintenanceEnables 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
public-tenders-es-eu
Server Details
Normalized search over public-sector tenders in TED (EU official procurement notices) -- Spain + EU
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- nexus-mcp-infra/public-tenders-es-eu
- GitHub Stars
- 0
- Server Listing
- public-tenders-es-eu
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
MCP client
Glama
MCP server
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
100% free. Your data is private.
Tool Definition Quality
A4.4/5.0
Tool DescriptionsA
Average 4.3/5 across 1 of 1 tools scored.
Server CoherenceA
Disambiguation5/5
With only one tool, there is no possibility of confusing it with another. Its purpose is clearly defined and unique within the server.
Naming Consistency5/5
The single tool name 'search_public_tenders' follows a clear verb_noun snake_case convention. While there are no other tools to compare against, the name itself is consistent and descriptive.
Tool Count4/5
One tool is slightly below the typical 3-15 range, but it is acceptable for a narrowly scoped read-only tenders search server. The tool is not trivial and covers the apparent core purpose.
Completeness4/5
The search tool includes useful parameters: country, keyword, CPV, recency, and limit. Minor gaps exist, such as missing sorting, pagination, or tender detail retrieval by ID, but these are not severe for the stated search use case.
Available Tools
1 toolsearch_public_tendersAInspect
Search public-sector tenders in TED (EU official procurement notices).
country is an ISO-3166 alpha-3 buyer-country code (e.g. 'ESP'), or
'ALL' for EU-wide. keyword full-text searches notice content.
cpv_prefix filters by CPV classification code prefix (e.g. '45' for
construction). days_back (1-90, default 30) bounds publication
recency. limit (1-50, default 20) caps result count.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| country | No | ESP | |
| keyword | No | ||
| days_back | No | ||
| cpv_prefix | No |
Tool Definition Quality
A4.3/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 burden. It describes the search as a read-only query over EU tenders and explicitly limits result count and recency, which implies a non-destructive behavior with bounded output. However, it does not disclose the output response shape or any rate limit or authorization considerations, leaving some behavior unstated.
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?
The description is a single lead sentence followed by a line per parameter, each line containing only necessary examples and constraints. It is concise, front-loaded, and every sentence earns its place.
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?
For a tool with five optional parameters and no output schema, the description provides enough to invoke it correctly: all parameters, representative examples, defaults, and valid ranges are explained. The main gap is that the returned structure is not described, but the absence of an output schema makes that less critical.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters5/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema provides no descriptions at all, yet the description fully covers every parameter: country codes and format, keyword semantics, CPV prefix usage with example, days_back range and default, and limit range and default. It adds substantial meaning beyond the bare input 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?
The description opens with a specific verb and resource: 'Search public-sector tenders in TED (EU official procurement notices).' This clearly identifies what the tool does and its domain. There are no siblings to differentiate, but the object and scope are unambiguous.
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?
No sibling tools are present, so there are no alternatives to compare against. The description conveys clear usage context by explaining how each parameter narrows the search and what values are valid, such as ISO-3166 alpha-3 country codes and 'ALL' for EU-wide. It stops short of explicit when-not-to-use guidance, but no ambiguity exists about the intended task.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceAccess Spain public procurement tender notices from PLACSP without API keys.8MIT
- AlicenseAqualityBmaintenanceExposes French and EU public procurement data (BOAMP + TED) as MCP tools for AI agents, enabling search for tenders, awards, and winner intelligence via typed filters.4MIT
- AlicenseNot gradedqualityAmaintenanceMCP server for Spain's official BOE auction portal: search judicial foreclosures, notarial and tax-agency auctions, get consolidated per-auction detail (assets, lots, bids, authority contacts) and computed legal thresholds (art. 671 LEC). Clean JSON, GDPR-safe, no headless browser.2AGPL 3.0
Try in Browser
Your Connectors
Sign in to create a connector for this server.