Distil — Machine-Native Public Data Refinery

Get EU TED Public Tender

get_eu_public_tender

Read-onlyIdempotent

Fetches condensed, token-optimized public procurement tender notice across the 27 EU member states from TED (< 1.5 KB). Returns contracting public authority, notice status, estimated budget in EUR, CPV classification code, and awarded suppliers.

Input Schema

TableJSON Schema

Name	Required	Description
`noticeId`	Yes	The European Union TED publication notice identifier (e.g. '2026-OJS-FR-CYBER-001').
`forceFresh`	No	Spend Control: When true, bypasses Edge KV cache and forces a real-time statutory primary registry call (applies 2.5x Freshness Inconvenience Surcharge). Default: false.
`maxAgeHours`	No	Spend Control: Maximum acceptable data age in hours (e.g. 48 for 2 days tolerance). If cache satisfies this, delivers sub-5ms at standard 1.0x Economy rate. Set to 0 to force live primary fetch.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`content`	Yes
`isError`	No

TDQS

A4/5.0

Behavior4/5

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

Annotations already mark the tool as read-only, idempotent, and non-destructive, so the safety profile is covered. The description adds useful behavioral context: it returns condensed, token-optimized data under 1.5 KB and lists the key fields included, which helps an agent understand response characteristics without needing to open the output schema.

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 front-loaded sentence that states the operation, scope, size constraint, and return contents with no filler. Every phrase 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?

With read-only annotations, a well-documented schema, and an output schema present, the description is nearly sufficient for correct invocation. The only notable gap is the lack of explicit routing guidance against sibling tools, but an agent with a noticeId can confidently select this tool.

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%, and the schema itself provides rich explanations for noticeId, forceFresh, and maxAgeHours, including caching and surcharge semantics. The main description adds no parameter-specific meaning beyond the schema, so the baseline score of 3 is appropriate.

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 begins with a specific verb and resource: 'Fetches ... public procurement tender notice across the 27 EU member states from TED.' It also lists the returned data fields, making it clear this is a single-notice retrieval tool and distinguishing it from sibling search and country-specific tender tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The intended use is implied: an agent should call this when it has a specific noticeId and needs a concise EU TED tender notice. However, the description never explicitly states when to prefer this over siblings like search_eu_tenders or get_es_public_tender, nor does it mention exclusions.

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

All Distil — Machine-Native Public Data Refinery tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4/5.0

Disambiguation5/5

Each tool maps to a distinct data product: country-specific filings, tender records/search, risk scoring, sanctions screening, and entity graphs. The search/get split cleanly separates discovery from retrieval, and even similar country-specific tools are clearly qualified by region and entity type.

Naming Consistency5/5

All tools use a consistent snake_case verb_noun pattern: get_* for retrieval and search_* for discovery, with country or region qualifiers where applicable. Cross-cutting tools like get_corporate_risk_score and get_tender_intelligence fit the same pattern without feeling out of place.

Tool Count4/5

At 16 tools, the server is slightly above the ideal 3-15 range, but the multi-country, multi-domain scope justifies nearly every tool. The set is heavier than a tightly focused server, yet no tool feels redundant.

Completeness4/5

The set covers the core read-only workflow well: search to find entities or tenders, get to retrieve records, plus analytical tools for risk, sanctions, and tender intelligence. Minor gaps exist, such as no Spanish company registry access and no UK tender search, but these are workable and do not block primary due-diligence workflows.

Resources

Need Help?