Skip to main content
Glama
Sirenic MCP server

Sirenic MCP server

Official

European company EU procurement awards (TED)

get_european_company_eu_procurement
Read-only

Find EU public-procurement contract awards won by a company using its national register ID, returning buyer, country, amount, CPV codes, official TED link, and co-winners.

Instructions

European public-procurement contract awards won by a company from Latvia (LV), Norway (NO), Belgium (BE), Denmark (DK), Finland (FI), Sweden (SE), Czechia (CZ), Slovakia (SK), Estonia (EE) or Lithuania (LT), from TED (Tenders Electronic Daily, EU Publications Office): award notices matched by the NATIONAL identifier in every form it takes on TED (variantes_identifiant): buyer, country, subject, notice-level amount, CPV codes, official TED link, co-winners proven legal persons (other names and IDs counted by reason, never named). Depending on the country, 40 to 94% of award notices carry a readable winner identifier (measured 2026-09-17): nombre_avis: 0 is a NON-conclusive absence. Czechia, Denmark, Estonia, Lithuania, Latvia, Norway, Sweden and Slovakia: legal persons only, a sole trader's IČO, a Danish sole proprietorship (enkeltmandsvirksomhed, read on the CVR profile), an Estonian sole proprietorship (FIE), a Latvian individual merchant (IK), a Norwegian sole proprietorship (ENK), a Swedish sole proprietorship (enskild näringsverksamhet) or a form not recognised as a legal person returns 404, not billed; in Lithuania, an individual enterprise (individuali įmonė, IĮ), its branch (individualios įmonės filialas) or representative office (individualios įmonės atstovybė), or an undecided form returns 404 as well. So does a Belgian entity without legal form or of a form off the whitelist, or a Finnish form off the YRMU codebook. France has get_french_company_eu_procurement, the UK get_uk_company_public_procurement. Live TED query, cached 24 h. Paid via x402 ($0.02 in USDC or EURC). When you report a result, cite its citation verbatim.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "pays": "<pays>",
      "id": "<id>"
    },
    "name": "get_european_company_eu_procurement"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesNational register identifier, e.g. 40003242722
paysYesISO-3166 alpha-2 country code: LV, NO, BE, DK, FI, SE, CZ, SK, EE or LT

Output Schema

NameRequiredDescriptionDefault
hintNoHow to settle the quote, present when payment_required is true.
quoteNoThe signable x402 payment requirements when payment_required is true: {x402Version, accepts[]} where each entry carries scheme, network, amount, asset and payTo (USDC and EURC options at the same numeric amount). Sign one entry and call again with `x_payment`.
resultatNoThe endpoint's JSON response when payment_required is false. Paid responses carry `source`, `disclaimer` and an Ed25519 signature, and every paid JSON response carries a `provenance` array (all tools since 2026-09-06): one entry per block served, with the official register, licence, version, `empreinte_sha256` (full snapshots), `as_of` date and `precision_as_of` (what that date means), plus the common per-block envelope: `etat` in a closed list (servi, absence_mesuree, absence_non_conclusive, partiel, perime, indisponible, sans_objet), `motif` when unavailable, `age_jours` (only for publication or ingestion dates), `couverture` (complete / partielle / non_mesurable with its measure) and `confiance` in bands (faible / moyenne / forte, only where a measure grounds it, never averaged across blocks). Read the states before the numbers: an absence_non_conclusive, indisponible or partiel block is never « nothing to report »; only absence_mesuree asserts an absence. Register codes: GET /v1/provenance/registres ; states, closed lists and reading rules: GET /v1/lecture (both free). The PDF tools carry no JSON envelope (the PDF report prints it).
free_tierNoFree API key offer for this tool, present with a quote.
payment_requiredYesTrue when this response is an x402 payment quote instead of data: settle one of the quote's `accepts` options and call the tool again with `x_payment`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/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 behavior beyond them: live TED query with 24h cache, x402 payment of $0.02 in USDC or EURC, 404 responses that are not billed, and per-country identifier coverage of 40–94%. Critically, it pre-empts a common failure mode by stating that `nombre_avis: 0` is a NON-conclusive absence rather than proof of no awards.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose and scope are front-loaded, but the body becomes a single dense paragraph that enumerates sole-proprietorship legal forms in six languages (enkeltmandsvirksomhed, FIE, IK, ENK, enskild näringsverksamhet, IĮ). Those details do affect 404 outcomes, so they earn their place marginally, but the parenthetical glosses could be condensed into a reference list without losing agent-relevant meaning.

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?

Given an output schema exists (so return values need no explanation), a 2-parameter fully-described input schema, and safety annotations, the description covers exactly the residual gaps an agent needs: billing, caching, coverage reliability, entity-type rejection, jurisdictional alternatives, and the requirement to cite the `citation` field verbatim. Nothing material is missing.

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?

Schema coverage is already 100%, so the schema carries the baseline. The description nonetheless adds real meaning: `id` is matched against the national identifier in every form it takes on TED (`variantes_identifiant`), and `pays` is not merely a code but a switch selecting country-specific legal-form whitelists that determine 404 behavior. It does not restate the regex constraints, which 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?

States a specific verb and resource ('European public-procurement contract awards won by a company'), names the data source (TED), and enumerates the exact country scope (LV, NO, BE, DK, FI, SE, CZ, SK, EE, LT). It also explicitly names the sibling tools that cover excluded jurisdictions (get_french_company_eu_procurement, get_uk_company_public_procurement), so an agent can differentiate 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 clear routing guidance for the excluded countries by naming France and UK alternatives, and specifies the entity-type preconditions that produce a 404 rather than a result. It stops short of stating when to prefer the generic get_eu_procurement_awards sibling over this country-scoped one, so the when-not guidance is incomplete rather than absent.

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

Deploy Server

Other Tools