Skip to main content
Glama
Sirenic MCP server

Sirenic MCP server

Official

EU procurement awards (TED)

get_eu_procurement_awards
Read-only

Find European public procurement awards won by a French company using its SIREN, with TED buyer, country, subject, amount, CPV codes and official links.

Instructions

European public procurement: government contracts and tender award notices won by a French company, from official TED data: buyer, country, subject, notice-level amount, CPV codes, official links, co-winners proven legal persons (other names and IDs counted by reason, never named). Identifier-matched only (SIREN/SIRET incl. spaced variants); coverage is eForms notices since 2023-10-25 above EU thresholds, and ~57% of award notices carry a usable identifier, so an empty list is not proof of absence. Complements get_french_company_public_procurement (French DECP, below-threshold). 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": {
      "siren": "<siren>"
    },
    "name": "get_eu_procurement_awards"
  }
}

Input Schema

NameRequiredDescriptionDefault
sirenYes9-digit SIREN

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.6/5.0
Behavior5/5

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

Goes well beyond readOnlyHint/openWorldHint: it discloses the temporal and threshold coverage boundary (eForms since 2023-10-25, above EU thresholds), a data-quality caveat (~57% of award notices carry a usable identifier, so empty is not absence), a resolution rule (identifier-matched only, SIREN/SIRET incl. spaced variants), privacy behavior (co-winners counted by reason, never named), and the x402 payment cost. A rare case where the description materially changes how an agent should interpret 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?

Purpose and scope are front-loaded, then coverage caveats, then the sibling relationship and payment/citation obligations — a sensible ordering. The prose is dense and parenthetical-heavy (field enumeration, 'other names and IDs counted by reason, never named'), but each clause carries operational information rather than filler.

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?

An output schema exists, so return structure needn't be explained, yet the description still flags the one return-value behavior an agent must honor: cite the `citation` field verbatim. Coverage limits, matching rules, cost, and the complementary sibling are all covered, leaving no material gap for a single-parameter lookup tool.

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 a single parameter at 100% schema coverage, the baseline is 3; the description adds matching semantics beyond the schema by specifying that matching is identifier-based and tolerant of spaced SIREN/SIRET variants. That clarifies how the required `siren` value is interpreted and what near-misses will or won't match.

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+resource with scope: 'government contracts and tender award notices won by a French company, from official TED data', then enumerates the fields returned (buyer, country, subject, amount, CPV, links, co-winners). It explicitly positions itself as complementing get_french_company_public_procurement (French DECP, below-threshold), so an agent can separate it from 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?

Names the sibling it complements and the differentiator (TED eForms above EU thresholds vs. French DECP below-threshold), which gives clear when-to-use context. It stops short of an explicit routing rule (e.g. 'use X when below threshold'), but the coverage statement plus the note that an empty list is not proof of absence is strong guidance.

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