Skip to main content
Glama
Bosco Labs Data

Bosco Labs Data

Official

EU public tenders (TED)

search_eu_tenders
Read-only

Find EU public procurement notices from TED by keyword, buyer country, or CPV sector, including open calls with deadlines and awards with winners. Filter by publication date and value.

Instructions

European public procurement notices from TED (Tenders Electronic Daily), the EU's official procurement journal: every above-threshold public contract in the EU/EEA, Switzerland and more, about 22,000 notices a week (source: official TED Search API). Use it to find open calls for tenders (with deadline and estimated value), contract awards (winners and awarded value) or planned purchases, by keyword, buyer country or sector.

Default: open calls for tenders published in the last 7 days. Newest first.

Returns one row per notice: notice_id, published, notice_type, title, description
(shortened), buyer_name, buyer_country, main_cpv, estimated_value, awarded_value,
currency, winner_names, deadline, procedure_type and ted_url (the notice; cite it).

Cost to the user: $0.002 per notice returned.

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_eu_tenders"
  }
}

Input Schema

NameRequiredDescriptionDefault
keywordsNoAll words must appear, any language, e.g. cloud
countriesNoBuyer countries, ISO codes, e.g. ['DE', 'FR']
cpv_codesNoCPV sector prefixes: 72 IT services, 45 construction, 3312 medical
max_resultsNoMax notices to return (1-100).
notice_typesNoOmit for open calls for tenders (contract_notice); contract_award = who won and for how much
published_toNo
min_value_eurNoLeaves out notices without an EUR value
published_fromNoDefault: 7 days ago

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.5

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnlyHint and openWorldHint, and the description adds substantial context beyond them: coverage breadth, recency default, sort order, the per-notice billing model ($0.002 per notice returned), and the instruction to cite ted_url. The cost-per-result disclosure is especially valuable for an agent deciding how to set max_results.

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 what the source is and what the agent can find, then defaults, then return shape, then cost — a sensible priority order. It is slightly verbose: the field list partially duplicates the output schema, and the default window is stated twice (prose and schema default).

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?

Covers source provenance, coverage, default query, sort order, row-level return contents, citation requirement and pricing — everything an agent needs before calling an 8-parameter, zero-required search tool. The output schema exists, so the field enumeration is a bonus rather than a gap-filler.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 88% schema coverage, most parameters are already documented in the schema, but the description adds the default window, the newest-first ordering, and ties result count to cost, which the schema does not convey. Gains are incremental rather than transformative since defaults like '7 days ago' also appear in 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?

Names a specific verb and resource (search EU public tender notices from TED) plus the exact scope: above-threshold EU/EEA/Swiss contracts at ~22,000 notices/week from the official API. It also enumerates the three content modes (open calls, contract awards, planned purchases), which lets an agent distinguish it from the US/SEC-oriented siblings 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?

Gives concrete use cases ('find open calls for tenders with deadline and estimated value', 'contract awards — winners and awarded value') and states the default behavior: open contract notices from the last 7 days, newest first. It stops short of explicit when-not-to-use guidance or naming an alternative tool for out-of-scope queries.

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