EU Tender Award Winners (TED)

search_tender_awards

Find out who wins EU public contracts in a market: competitors, partners or sales leads. Searches TED contract award notices by keywords, CPV, buyer countries, winner name and look-back days: winner, winner country, national ID, SME flag, awarded value and currency, decision date, buyer, CPV and links. Use when sizing a public-sector market or researching a competitor's contracts. $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_tender_awards"
  }
}

Input Schema

Name	Required	Description
`cpv`	No	Comma-separated CPV codes
`days`	No	Look-back days (default 365)
`limit`	No	Max results (default 20)
`query`	No	Keywords
`winner`	No	Winner name contains
`countries`	No	Comma-separated ISO2 buyer countries
`payment_signature`	No	x402 v2 PAYMENT-SIGNATURE header value. Omit to receive payment requirements.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 16, 2026

TDQS

A4.1/5.0

Behavior4/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 — and it discloses the commercially critical trait that this is a paid call ($0.03 per call, USDC on Base via x402). It does not cover rate limits, failure modes, or result caps beyond the schema's limit parameter, but the payment model disclosure is substantial behavioral context.

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?

Front-loaded with the outcome value and then the mechanics, one dense but purposeful block with no filler. Slightly long, but every clause maps to either search inputs, returned fields, or pricing.

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 no output schema, the description usefully enumerates the return fields (winner, country, national ID, SME flag, awarded value and currency, decision date, buyer, CPV, links) and explains the payment handshake indirectly. Combined with 100% schema coverage of inputs, an agent has enough to call it correctly.

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 the schema already documents all seven parameters including defaults and bounds. The description restates the searchable dimensions (keywords, CPV, buyer countries, winner name, look-back days) without adding syntax or format detail, so it stays at the baseline.

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: searches TED contract award notices to find who wins EU public contracts. It names the searchable dimensions and the returned fields, so an agent knows exactly what this tool does without opening the schema.

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?

Explicitly gives the use case: sizing a public-sector market or researching a competitor's contracts. No alternatives or exclusions are named, but there are no sibling tools to disambiguate against, so the guidance is as complete as the context allows.

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

All EU Tender Award Winners (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?