Skip to main content
Glama
Sirenic MCP server

Sirenic MCP server

Official

French company file (choose blocks)

get_french_company_file
Read-only

Retrieve a French company's full registry file in one call by selecting only the data blocks you need, avoiding chained requests and paying per requested block.

Instructions

Full French company file in ONE call, paying only for the blocks you ask for: for when you need several things about the same company and do not want to chain calls. The identity base is $0.005; add any of etablissements, alertes_bodacc, contentieux, finances, marches_publics, marches_publics_ue, lobbying, risques_industriels, agrements, pi, documents, facturation_prep, score. Each block costs exactly what its dedicated endpoint costs, and the total is capped at $0.35. Any block that cannot be served is NAMED with a reason from a closed list: aucune_donnee (a negative answer, e.g. no patents), non_diffusible (GDPR/partial disclosure), non_couvert (not a proven legal person), panne_amont (upstream register down), stock_perime (local copy past its age limit), collecte_en_cours (local stock empty or never loaded) or identite_incomplete (incomplete identity). For a verdict rather than raw blocks, use get_french_company_intelligence ($1.00). An identity whose administrative status or legal category is missing in Sirene is served with blocs_absents (raison identite_incomplete) and a partial provenance. Blocks built on it (score, facturation_prep) are absent for that reason (identite_incomplete). If no requested block is served and one is down, stale (stock_perime) or with its local stock empty or never loaded (collecte_en_cours), the call returns 503 (a retry may serve a down block); else if one is refused for that reason, 404 identite_incomplete; neither is charged. Asking for score on a sole proprietorship, a restricted-diffusion unit or a group without legal personality refuses the whole file: 400 with the exact code, never charged. Partial diffusion (rule diffusion_partielle_nom_retenu_et_compte): for a unit not proven to be a legal person, identite.denomination and every documents nom_document are null, counted in ecartes.diffusion_partielle; facturation_prep.destinataire.denomination is null, uncounted, and destinataire.information states the partial diffusion. Public procurement block: 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). Paid via x402 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>",
      "blocs": "<blocs>"
    },
    "name": "get_french_company_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
blocsYesComma-separated blocks, e.g. finances,pi,score. Available: etablissements, alertes_bodacc, contentieux, finances, marches_publics, marches_publics_ue, lobbying, risques_industriels, agrements, pi, documents, facturation_prep, score
sirenYes9-digit SIREN, e.g. 552032534

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?

The annotations only declare readOnlyHint=true and openWorldHint=true, while the description adds substantial behavioral context: per-block pricing, a $0.35 cap, exact failure reason codes, 503/404/400 conditions, partial-diffusion handling, and public-procurement naming rules. These details go well beyond the annotations and remain consistent with them.

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 description is front-loaded with purpose and pricing, which is good, but it is a very long and dense paragraph that mixes core selection guidance with many edge-case rules. The information is mostly relevant, yet the lack of structure and the sheer volume of detail reduce scannability.

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 paid, open-world, multi-block retrieval tool with an output schema, the description covers pricing, block selection, major failure modes, partial-diffusion handling, and key refusal conditions. It does not need to explain return fields because an output schema exists, and it provides enough context for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema already documents siren and the comma-separated blocs parameter, but the description adds meaning around block selection: the identity base cost, block-specific pricing, score refusal conditions, facturation_prep dependency behavior, and closed-list failure reasons for requested blocks. This materially improves how an agent chooses and interprets the parameters.

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 states a specific verb and resource: it returns a full French company file in one call while allowing the caller to choose blocks. It explicitly contrasts itself with get_french_company_intelligence for a verdict rather than raw blocks, making the tool's role distinguishable from a related sibling.

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?

It gives a clear selection condition: use this when several things are needed about the same company and you do not want to chain calls, and it names get_french_company_intelligence as the alternative for a verdict. It does not explicitly name dedicated single-block endpoints for narrow needs, but the 'several things' framing implies that single-block retrieval is a different case.

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