Distil — Machine-Native Public Data Refinery

Get Spain Public Tender

get_es_public_tender

Read-onlyIdempotent

Fetches a verified, token-optimized statutory public sector procurement tender from Spain's aggregated PLACSP syndication feed (CODICE XML) by expediente identifier (< 1.5 KB). Returns contracting authority, tender title, budget valuation in EUR, contract type, CPV code, awarded contractor, and award date. Note: PLACSP has no live single-tender lookup API, so this serves from Distil's continuously-synced data moat — use search_es_tenders first if you don't already have the exact expediente ID, and expect 'not found' for tenders outside the aggregated feed's recent window.

Input Schema

TableJSON Schema

Name	Required	Description
`tenderId`	Yes	Official Spanish public tender folder identifier or PLACSP expediente reference (e.g. '2024/00123').
`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.6/5.0

Behavior5/5

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

Beyond the annotations (readOnly, openWorld, idempotent), the description discloses the underlying data source is a syndicated feed with no live single-tender API, that it serves from a continuously-synced cache, and that it may return not-found for older tenders. This gives the agent essential expectations not captured in structured metadata.

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?

The description is dense and informative, front-loading the core function and return fields before the context note. It is slightly verbose with phrases like 'Distil's continuously-synced data moat,' but every sentence contributes actionable context.

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?

The tool has an output schema and comprehensive annotations, and the description fills the remaining gaps: data provenance, freshness limitations, alternative tool routing, and expected not-found behavior. Together this fully equips an agent to use the tool 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%, with each parameter already documented with details such as examples and defaults. The description reinforces tenderId as the lookup key but adds no new semantic meaning beyond the schema, so baseline 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 uses a specific verb ('fetches') with a clear resource: Spain's PLACSP syndication feed by expediente identifier. It distinguishes itself from siblings by naming the specific country, data feed, and identifier type, and even references the sibling search_es_tenders, making the tool's purpose unmistakable.

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

Usage Guidelines5/5

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

Explicitly tells the agent to use search_es_tenders first if the exact expediente ID is not known, and warns about 'not found' results outside the recent feed window. It also explains the lack of a live API, providing clear context for when this tool is appropriate versus alternatives.

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?