Skip to main content
Glama
Sirenic MCP server

Sirenic MCP server

Official

French public buyer profile

get_french_public_buyer_profile
Read-only

Retrieve a French public buyer's procurement profile by SIRET—contract volumes, top CPV segments, incumbent suppliers, expiring contracts, and buying habits for sourcing meetings.

Instructions

Procurement profile of a French public buyer (by SIRET): contract volumes by year, top CPV segments, incumbent suppliers with their contracts expiring within 18 months, framework-agreement share, share of amounts that are envelopes rather than firm prices, share of contracts with declared subcontracting, share granting an advance, dominant CCAG and price type, publishing platform, average bids received per tender and median publication delay: the buying habits to know before a sourcing meeting. From official DECP open data. Paid via x402 ($0.02 in USDC or EURC). Names are served for legal persons proven by their Sirene legal category only: a sole proprietorship, a group of natural persons or a category in doubt never has its name served and keeps its SIREN or SIRET, the omissions counted without identity in ecartes, over the entries the response serves (rule R1). A contract subject that names a person by a civility followed by a capital letter (M., Mme, Monsieur, Madame, Maître…) is served null, counted without identity in ecartes; the contract stays (rule R1). 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": {
      "siret": "<siret>"
    },
    "name": "get_french_public_buyer_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
siretYes14-digit SIRET of the public buyer, e.g. 26310012500016 (CHU de Toulouse)

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

A3.9/5.0
Behavior5/5

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

Beyond readOnlyHint/openWorldHint, the description discloses economics and access mechanics ('Paid via x402 ($0.02 in USDC or EURC)'), which an agent must know before calling, and two substantive data-handling rules: legal-person name service gated on Sirene legal category (sole proprietorships, groups of natural persons and doubtful categories keep their SIREN/SIRET and are counted as omissions in ecartes), and civility-prefixed contract subjects served as null while the contract itself remains. It also imposes an output obligation ('cite its `citation` verbatim'). These are non-obvious behavioral traits that no annotation or schema conveys.

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?

The purpose and the exhaustive field list are front-loaded, which is correct, but the content arrives as one very long colon-delimited sentence followed by dense legalistic passages ('a group of natural persons or a category in doubt never has its name served and keeps its SIREN or SIRET'). The redaction rules earn their place, yet the enumeration of eleven profile dimensions could be compressed without loss, and the repeated 'rule R1' tags add bulk without adding meaning for an agent.

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?

For a single-parameter, read-only lookup with an output schema available, the description covers everything an agent needs: what the payload contains, that it is paid and how much, the privacy redaction behavior that could otherwise make a returned null look like an error, and the mandatory citation of the returned `citation`. Return-field formats are correctly left to the output schema.

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 coverage is 100% and the single parameter already carries a pattern, a format constraint and a worked example (CHU de Toulouse), so the schema does the heavy lifting. The description only restates '(by SIRET)' without adding syntax, validity, or failure-mode detail beyond what the schema provides. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The definition names a specific resource (procurement profile of a French public buyer, keyed by SIRET) and enumerates precisely what the profile contains: contract volumes by year, CPV segments, expiring incumbents, framework-agreement share, envelope vs firm-price share, subcontracting, advance, CCAG/price type, platform, average bids, median publication delay. That is far more than a restatement of the title. It stops short of 5 because it never names the adjacent siblings (get_french_company_public_procurement, find_expiring_french_public_contracts) that an agent would have to choose between; the buyer-vs-company distinction is only implicit in the phrase 'French public buyer'.

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 phrase 'the buying habits to know before a sourcing meeting' gives a concrete use case, which is genuine context rather than none. However, there is no explicit when-to-use/when-not statement, no named alternative for the company-side or expiring-contracts view, and no guidance on what to do if the SIRET belongs to a private entity. Usage is implied rather than directed.

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