Skip to main content
Glama
Sirenic MCP server

Sirenic MCP server

Official

French company PDF report

get_french_company_pdf_report
Read-only

Generate a shareable due-diligence PDF for a French company by SIREN, covering identity, officers, legal alerts, financials, sanctions, and a public verification link.

Instructions

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior5/5

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

Beyond the readOnlyHint/openWorldHint annotations, the description discloses a great deal the agent could not otherwise know: a $0.50 USDC/EURC x402 charge, that refused SIRENs are never charged, the exact 404 identite_incomplete and 400 refusal codes with response body fields, the partial-diffusion naming rule, and the verification link embedded in every page footer. It also states the return encoding (base64 PDF).

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?

The core purpose is front-loaded in the first clause and nearly every sentence carries operational value (payment, refusals, footer link, return format). It is a dense single paragraph, though, with several domain-specific codes and rule names packed together, which makes it harder to scan than a lightly structured version would be.

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 one-parameter tool with no output schema, the description covers everything needed: what the PDF contains, how it is returned (base64), what it costs and how payment works, and precisely which inputs are rejected and with what codes. An agent could invoke this correctly without consulting any other source.

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?

With a single parameter at 100% schema coverage, the schema already fully documents the 9-digit SIREN. The description adds meaningful surrounding semantics — that the SIREN's administrative status and legal category are validated against Sirene and that certain entity types are rejected — but nothing about the parameter's format or syntax beyond what the schema states.

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?

The description opens with a specific verb and resource (on-demand PDF report of a French company) and immediately characterizes the artifact as a shareable due-diligence dossier with named contents (identity, officers, legal alerts, financials, sanctions screening). It is clear what the tool produces, but it never explicitly contrasts itself with close siblings like get_french_company_kyb_file or get_french_company_file, so the agent must infer that the differentiator is the PDF format.

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 rather than stated: the 'shareable due-diligence dossier' framing and the note that any PDF recipient can open the verification link suggest when to reach for this tool. The refusal conditions (incomplete Sirene data, non-legal-persons, partial diffusion) are well specified, but there is no explicit 'use X instead when you only need JSON data' routing against the many sibling file/kyb tools.

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