Skip to main content
Glama
Sirenic MCP server

Sirenic MCP server

Official

List French company documents (INPI)

list_french_company_documents
Read-only

List official INPI RNE filings for a French company by SIREN, including legal deeds and annual accounts, and return document IDs to download PDFs.

Instructions

List official documents filed by a French company at the INPI RNE registry: legal deeds (statutes, general-meeting minutes, mergers...) and filed annual accounts, with document IDs to download the PDFs. Partial diffusion (rule diffusion_partielle_nom_retenu_et_compte): for a unit not proven to be a legal person, denomination and every nom_document are null, each counted in ecartes.diffusion_partielle; the filings stay listed. 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": "list_french_company_documents"
  }
}

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

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

Beyond readOnlyHint/openWorldHint, the description discloses the paid x402 model ($0.02 in USDC or EURC), the null-field behavior under partial diffusion and how those records are counted in ecartes.diffusion_partielle, and the requirement to cite `citation` verbatim. These are exactly the non-obvious traits an agent needs and none contradict the annotations.

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?

Front-loaded with purpose, then edge-case semantics, payment, and citation rule in short declarative clauses. The diffusion-partielle sentence is dense with French field names, adding some parsing burden, but every sentence carries operational value.

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-shape explanation is unnecessary; the description instead covers what an output schema cannot: payment mechanics, null-field edge cases under partial diffusion, and the citation obligation. Nothing material is missing for a one-parameter read tool.

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% for the single `siren` parameter (9-digit pattern), so the schema already carries the semantics. The description adds nothing about the parameter itself, which is acceptable but is the baseline case.

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 ('List official documents filed by a French company') plus the exact registry (INPI RNE) and the two content classes (legal deeds, annual accounts). It also distinguishes itself implicitly from the download sibling by noting it returns 'document IDs to download the PDFs'.

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?

There is no explicit when-to-use / when-not clause or named alternative, but usage is strongly implied: the tool returns IDs to feed a download step, and the payment cost is stated. An agent must still infer that this is the discovery step before download_french_company_document.

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