Search EU TED procurement notices by CPV, country, keyword, value, or type.
Run the Apify TED tender monitor for new or changed EU procurement notices filtered by CPV, country, keyword, value, and notice type. Supports sample mode, stateful monitoring, JSON datasets, and signed webhooks.
| Name | Required | Description | Default |
|---|---|---|---|
| cpvCodes | No | Optional 2-8 digit CPV code prefixes such as 72 for IT or 45 for construction. | |
| keywords | No | Optional full-text terms or phrases, OR-matched by TED. | |
| stateKey | No | Optional advanced override for deliberately sharing monitor state across Tasks. | |
| countries | No | Optional ISO 3166 alpha-3 buyer country codes such as DEU, FRA, or ESP. | |
| sampleMode | No | Return a bounded free preview without writing monitor state or triggering tender charges. | |
| webhookUrl | No | Optional HTTPS endpoint that receives delivered tender records after dataset and state delivery. | |
| minValueEur | No | Client-side minimum for known procedure-level EUR values. | |
| noticeTypes | No | Official TED notice-type codes. Defaults to competition notices. | |
| lookbackDays | No | Minimum overlap window for late publication and missed schedules. | |
| maxNewPerRun | No | Maximum new or changed tenders delivered and charged in one run. | |
| webhookSecret | No | Required with webhookUrl. Used for the X-Watch-Signature HMAC-SHA256 header. | |
| includeChangeNotices | No | Include change and corrigendum notices alongside the selected notice types. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already mark the tool open-world, non-idempotent, and non-destructive; the description adds that it is stateful, can emit JSON datasets, and supports signed webhooks, which is useful behavioral context beyond the hints. It does not contradict the annotations. The main description could more directly warn about charges or state writes, but sample mode is mentioned and the schema fills in the details.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences: the first front-loads purpose and scope, the second lists supported capabilities in a compact noun phrase list. No wasted words or repetition of schema details. Excellent density.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a 12-parameter tool with no output schema, the description gives a high-level map of inputs and outputs ('JSON datasets', 'signed webhooks') and names the major operational modes. The absence of an output schema is partly mitigated by mentioning datasets and tender records in schema fields, but the main description does not describe the default run behavior or return shape in detail. Still, combined with the rich parameter schema, it is sufficiently complete for invocation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, and every parameter has its own description, default, and constraints, so the baseline is 3. The tool description summarizes the filter categories (CPV, country, keyword, value, notice type) but adds no parameter-specific detail beyond the schema. It neither compensates for gaps nor introduces confusion.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description opens with a specific action ('Run the Apify TED tender monitor') and a concrete resource ('new or changed EU procurement notices'), then enumerates the filter dimensions (CPV, country, keyword, value, notice type). There are no sibling tools, so no differentiation is needed, and the title reinforces the domain. This is fully unambiguous.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description clearly frames the tool as a monitor for new or changed notices, which tells an agent when to reach for it, and the second sentence advertises sample mode for previews versus stateful monitoring for ongoing runs. It does not list explicit exclusions or alternatives, but with no siblings the context is sufficient. A small deduction for not stating prerequisites such as sampleMode=false for paid runs, though that is covered in the schema.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.
Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
GitHub identity — fastest for official registry listings. For a namespace such as io.github.alice/server, link the matching GitHub user or an account that owns the GitHub organization, then choose Claim with GitHub.
HTTP challenge — works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at /.well-known/glama.json on the same origin as the connector, then choose Check HTTP challenge.
DNS challenge — works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.
The HTTP ownership file has this structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"claim": "glama_claim_..."
}Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.
If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.
For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.
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
To improve your MCP server's ranking:
Claim ownership of the server listing
Complete the server profile with an accurate description and thumbnail
Provide a test profile so Glama can connect to and evaluate the server
Keep tool definitions clear and complete to earn a high Tool Definition Quality Score (TDQS)
Route real usage through the Glama Gateway; more recorded successful server uses also improve the ranking
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.
No comments yet. Be the first to start the discussion!
Normalized search over public-sector tenders in TED (EU official procurement notices) -- Spain + EU
Search EU public tenders across TED and 8 national portals. Monitor, match, and analyse procurement.
Search public procurement notices from 17 sources across Germany, the EU and the UK. Read-only.
TED MCP — Tenders Electronic Daily (EU public procurement)
Add one secure layer between your agents and this server.
With only one tool, there is no possibility of confusion or overlap between tool purposes. The single tool's description clearly defines what it does.
The name follows a snake_case pattern but includes an opaque generated prefix ('uplifted_novice_vbl--') that does not align with conventional verb_noun naming. It is readable and descriptive enough, but the prefix makes it feel inconsistent with common tool naming standards.
A single tool for a domain like EU tender monitoring is very thin. The tool bundles many features, but the server lacks separate operations for managing monitors, retrieving results, or handling datasets, making the surface feel incomplete for the scope.
The tool can start a monitoring run with filters, but there are no accompanying tools to check run status, retrieve results, manage saved monitors, or configure webhooks independently. This leaves significant gaps for an agent that needs to interact with the monitoring lifecycle beyond the initial run.
