Skip to main content
Glama
Sirenic MCP server

Sirenic MCP server

Official

Download French company document

download_french_company_document
Read-only

Download official French company PDFs from the INPI RNE registry using IDs from list_french_company_documents; annual accounts are open to any payer, while legal deeds require an API key.

Instructions

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
document_idYesDocument `id` from list_french_company_documents

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only declare readOnlyHint/openWorldHint; the description adds far more: auth requirements per type, the 401 compte_requis outcome with no charge, pricing ($0.10 in x402 USDC/EURC or credits), base64 PDF return with 1-10 MB size, and the personal-data 404 exception. That is richly beyond structured data.

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 prerequisite are front-loaded, and nearly every clause carries a distinct fact (auth, price, error codes, payload). The final sentence is a long run-on that packs three ideas together and could be split for faster scanning.

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?

With no output schema, the description covers the return value (base64 PDF, typical 1-10 MB), cost, authentication per document family, and both failure modes (401 compte_requis, 404 diffusion_partielle), so an agent has everything needed to call it correctly and interpret outcomes.

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 baseline is 3; the description earns an extra point by explaining what the enum values actually are ('bilans' = filed annual accounts, 'actes' = statutes/general-meeting minutes) and which one imposes an auth requirement. It adds no detail on document_id beyond the 24-hex format already in the schema.

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+source: 'Download an official company document (PDF) from the INPI RNE registry.' It also routes the agent to the prerequisite sibling (list_french_company_documents) for IDs, so it is clearly distinguishable from the listing tool.

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?

Gives explicit conditions per document family: bilans open to any payer, actes reserved to identified Sirenic accounts since 2026-09-19 and requiring api_key. It also explains the 404 diffusion_partielle case, which is effectively a when-not-to-expect-a-result rule.

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