EU Public Tender Search (TED)

search_tenders

Find open EU public tenders a company could bid on. Searches TED (Official Journal S) for open EU/EEA procurement notices by keywords, CPV codes, buyer countries and minimum days to deadline. Returns notice ID, title, buyer, country, CPV, deadline, estimated value, procedure and links, newest first. Use when building a bid pipeline or sales leads from public procurement. $0.03 per call, USDC on Base (x402).

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

Name	Required	Description
`cpv`	No	Comma-separated CPV codes
`limit`	No	Max results (default 20)
`query`	No	Keywords
`countries`	No	Comma-separated ISO2 buyer countries
`payment_signature`	No	x402 v2 PAYMENT-SIGNATURE header value. Omit to receive payment requirements.
`min_days_to_deadline`	No	Minimum days left to deadline

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 16, 2026

TDQS

A4.2/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does a good job: it discloses the data source, the supported filter axes, the result ordering ('newest first'), and the cost model ('$0.03 per call, USDC on Base (x402)'). It omits operational traits such as rate limits, result-set pagination beyond the limit parameter, and failure behavior on missing payment, which keeps it out of the top score.

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?

Four sentences, front-loaded with purpose then scope then return shape then cost, with no filler. Minor redundancy in repeating 'open' and 'EU/EEA procurement notices' costs it the top mark.

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?

Because there is no output schema, the description usefully enumerates the return fields (notice ID, title, buyer, country, CPV, deadline, estimated value, procedure, links) and the ordering, and it covers the payment prerequisite that annotations would otherwise flag. Nothing an agent needs before calling is missing.

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 100%, so all six parameters are already documented, establishing a baseline of 3. The description restates the filter concepts (keywords, CPV codes, buyer countries, minimum days to deadline) but adds no format or syntax detail beyond the 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?

States a specific verb and resource ('Find open EU public tenders a company could bid on') and pins the underlying source to TED / Official Journal S, so the agent knows exactly what corpus is being searched. The scope (open EU/EEA procurement notices) is unambiguous even without sibling tools to distinguish from.

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?

'Use when building a bid pipeline or sales leads from public procurement' gives a clear situational trigger for invocation. It stops short of exclusions or alternative tools, but with no siblings listed there is nothing to route away from.

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

All EU Public Tender Search (TED) tools Inspect

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.

Resources

Need Help?