Skip to main content
Glama

Download French company document

download_french_company_document
Read-only

Download an official company document (PDF) from the INPI RNE registry. Use IDs from list_french_company_documents. Filed annual accounts (type bilans): any payer, x402 or api_key. Legal deeds (type actes: statutes, general-meeting minutes) are RESERVED to identified Sirenic accounts since 2026-09-19 because they carry personal data: pass api_key, otherwise 401 compte_requis and nothing is charged. Returns the PDF as base64; documents typically weigh 1-10 MB. $0.10 (x402 in USDC or EURC, or account credits). A filing of a unit the INSEE publishes partially (a sole trader who objected to the publication of their data) that is not proven to be a legal person returns 404 diffusion_partielle, not charged: its PDF carries the person and is not served.

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": {
      "type": "<type>",
      "document_id": "<document_id>"
    },
    "name": "download_french_company_document"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeYesDocument family from the list tool
api_keyNoOptional Sirenic API key (srn_live_…) to pay with prepaid credits instead of x402, with no wallet needed. Get one at https://api.sirenic.eu/compte?utm_source=api&utm_campaign=mcp. Ignored when x_payment is provided (the signed payment wins). On insufficient balance the tool returns a credits error, not an x402 quote. Each key has a daily spending cap (Paris time, 100 EUR unless set from 1 to 2000 EUR in the account): a call that would exceed it returns the plafond_cle_atteint error (HTTP 429), nothing charged, until midnight Paris time.
x_paymentNoOptional signed x402 PAYMENT-SIGNATURE header value. Omit to receive the payment quote.
document_idYesDocument `id` from list_french_company_documents

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / api_key / description
      Previous value: -"Optional Sirenic API key (srn_live_…) to pay with prepaid credits instead of x402, with no wallet needed. Get one at https://api.sirenic.eu/compte?utm_source=api&utm_campaign=mcp. Ignored when x_payment is provided (the signed payment wins). On insufficient balance the tool returns a credits error, not an x402 quote."New value: +"Optional Sirenic API key (srn_live_…) to pay with prepaid credits instead of x402, with no wallet needed. Get one at https://api.sirenic.eu/compte?utm_source=api&utm_campaign=mcp. Ignored when x_payment is provided (the signed payment wins). On insufficient balance the tool returns a credits error, not an x402 quote. Each key has a daily spending cap (Paris time, 100 EUR unless set from 1 to 2000 EUR in the account): a call that would exceed it returns the plafond_cle_atteint error (HTTP 429), nothing charged, until midnight Paris time."
  2. Changed1 schema field changed
    • removedInput schema / additionalProperties
      Removed value: -false
  3. Added
  4. Removed
  5. Changed1 schema field changed
    • addedInput schema / properties / api_key
      Added value: +{
      +  "description": "Optional Sirenic API key (srn_live_…) to pay with prepaid credits instead of x402 — no wallet needed. Get one at https://api.sirenic.eu/compte. Ignored when x_payment is provided (the signed payment wins). On insufficient balance the tool returns a credits error, not an x402 quote.",
      +  "type": "string"
      +}
  6. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Beyond readOnlyHint/openWorldHint, the description discloses price ($0.10), payment rails, base64 return format, document size (1-10 MB), the charging rules on failure, and the legal-person restriction on partially published filings. That is far richer than the annotations. It stops just short of stating rate limits or whether the download is retryable/idempotent, which keeps it from a 5.

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 the purpose and the ID source before the branching rules. However, the final sentence is a dense run-on that packs the partial-publication edge case, the error code, the charging rule, and the rationale into one breath; it would read better split or moved into a caveat block.

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, authenticated download with no output schema, the description covers everything an agent needs: pricing, auth paths, per-family restrictions, return encoding and size, and the specific errors that mean 'do not retry, do not expect a charge'. Nothing material is left undocumented.

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 100%, so the baseline is 3, but the description adds real meaning: it gives concrete content for the 'actes' enum value (statutes, general-meeting minutes), says api_key is mandatory for that family, and ties x_payment to the $0.10 cost. The api_key precedence and daily cap are already covered by the schema, so this is value added rather than duplication.

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 ('Download an official company document (PDF) from the INPI RNE registry') and explicitly routes the agent to list_french_company_documents for the IDs, which separates it from the metadata siblings in the catalog.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly splits the two document families and their preconditions: 'bilans' works for any payer, while 'actes' are RESERVED to identified Sirenic accounts and require api_key. It also names the exact failure modes (401 compte_requis, 404 diffusion_partielle) so an agent knows when to bail out rather than retry.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.