Skip to main content
Glama

French company PDF report

get_french_company_pdf_report
Read-only

On-demand PDF report of a French company: a shareable due-diligence dossier (formatted KYB file: identity, officers, legal alerts, financials, sanctions screening; includes the AI health summary when cached). Every page footer carries a public verification link (/verifier/ and the response's verification number) that whoever receives the PDF can open. Returns the PDF as base64. A SIREN whose administrative status or legal category is missing in Sirene is refused: 404 identite_incomplete (body: siren, champs_absents, fiche), never charged. Fully disclosed legal persons only: a sole proprietorship, a restricted-diffusion unit or a group without legal personality is refused, 400 with the exact code, never charged. Partial diffusion (rule diffusion_partielle_nom_retenu_et_compte): the name of a unit not proven to be a legal person is left out, the PDF prints its SIREN. Paid via x402 ($0.50 in USDC or EURC).

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": "get_french_company_pdf_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
sirenYes9-digit SIREN
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.

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

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

Goes well past the annotations (readOnlyHint/openWorldHint) by disclosing the return encoding (PDF as base64), the embedded verification link and verification number, the 404 identite_incomplete refusal with body fields and the 'never charged' guarantee, the 400 refusal for non-legal-person entities, the partial-diffusion name-suppression rule, and the $0.50 x402 price in USDC or EURC. These are exactly the failure modes and cost implications an agent needs before calling a paid, mutating-free but charged operation.

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 output format before the error and payment rules, and each sentence carries distinct information (contents, footer link, refusals, pricing). It is dense and parenthetical — the 'Partial diffusion (rule diffusion_partielle_nom_retenu_et_compte)' sentence is heavy — but no sentence is filler.

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 carries the return-value burden and does so ('Returns the PDF as base64', plus what the footer contains). It also covers the refusal paths and the payment model, so an agent knows both what it gets and what it costs, which is complete for a single-required-parameter 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 description coverage is 100%, so the siren pattern, api_key credit path, daily cap and x_payment quote flow are already documented in the schema. The description adds only that payment is x402-priced at $0.50 and restates the SIREN-driven refusal conditions; it adds no new meaning for api_key or x_payment and does not explain precedence between them, which the schema already does.

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?

States a concrete verb and artifact: 'On-demand PDF report of a French company: a shareable due-diligence dossier' and enumerates the dossier's contents (identity, officers, legal alerts, financials, sanctions screening). The artifact type (PDF, base64) and the footer verification link make the output clearly distinct from data-returning siblings, but the description never names any sibling (e.g. the KYB file or file tools) to route an agent between them explicitly.

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?

Usage is implied by 'shareable due-diligence dossier' and 'whoever receives the PDF can open' — i.e. use this when a document must be handed to a third party. It also gives clear when-NOT conditions (incomplete Sirene identity, non-legal-person entities) with the exact error codes. However it gives no explicit alternative for callers who want the same data as JSON, leaving the agent to infer the boundary with the many sibling company tools.

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.