Skip to main content
Glama
Sirenic MCP server

Sirenic MCP server

Official

French company KYB file

get_french_company_kyb_file
Read-only

Retrieve a complete KYB due-diligence file for a French company, consolidating identity, officers, legal alerts, court decisions, financials, sanctions screening, VAT, and completeness score.

Instructions

Complete KYB (Know Your Business) file for a French company in one call: a comprehensive BUNDLE consolidating identity, officers, BODACC legal alerts, commercial-court decisions linked to the company (Judilibre, since 2026-09-24: the 20 most recent with official links; partial coverage, so zero decisions is a non-conclusive absence, never 'no litigation'), filed financials, sanctions screening of the company and each officer (6 official lists), VAT number and a completeness score. Use this when you want the whole due-diligence picture at once; if you only need one part, call the dedicated tool instead (get_french_company_profile, get_french_company_legal_alerts, get_french_company_court_decisions, get_french_company_financials, or screen_sanctions_lists): they are cheaper. Every block carries its provenance: official register, licence, version and as_of date, plus precision_as_of telling whether that date is the upstream official publication, Sirenic's ingestion or a live consultation. The file ends with verification (number and public link, /verifier/): whoever receives the file can check it. A SIREN whose administrative status or legal category is missing in Sirene is refused: 404 identite_incomplete (body: siren, champs_absents, fiche), never charged. get_french_company_profile still serves its profile, with that caveat. 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): a unit not proven to be a legal person is served with identite.denomination null, counted in identite.ecartes.diffusion_partielle. Paid via x402 ($0.15 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": "get_french_company_kyb_file"
  }
}

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.4/5.0
Behavior4/5

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

Annotations only say readOnly/openWorld, so the description carries real weight and does: $0.15 x402 payment, 404 identite_incomplete and 400 refusal paths that are 'never charged', partial-diffusion handling with identite.denomination null, per-block provenance (licence, version, as_of, precision_as_of), and the verification/citation requirement. It also discloses the Judilibre coverage limit and warns that zero decisions is non-conclusive — exactly the kind of caveat annotations cannot express. Minor deduction for not stating rate limits or latency, but the behavioral picture is unusually complete.

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 the cheaper-alternatives routing are front-loaded, and nearly every clause carries decision-relevant information. It is dense and slightly repetitive ('never charged' twice, the partial-diffusion rule spelled out at length), which costs it a point, but there is no filler prose.

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, yet the description still orients the agent to what comes back (provenance fields, ecartes.diffusion_partielle, the verification block) without duplicating the schema. Cost, refusal codes, coverage caveats, and citation obligations are all covered for a paid multi-block aggregator.

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?

There is a single required parameter with 100% schema description coverage, so the baseline is 3. The description implies the siren input through the refusal rules ('A SIREN whose administrative status ... is refused') but adds no format, normalization, or validation detail beyond the schema's 9-digit pattern.

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?

Opens with a specific verb+resource ('Complete KYB file for a French company in one call') and immediately enumerates the bundle contents: identity, officers, BODACC alerts, court decisions, financials, sanctions screening, VAT, completeness score. It explicitly distinguishes itself as the aggregator versus the single-purpose siblings, so an agent can choose without opening a schema.

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?

States both directions: 'Use this when you want the whole due-diligence picture at once' and 'if you only need one part, call the dedicated tool instead' with four named alternatives plus a cost reason ('they are cheaper'). It also gives the fallback path when this tool refuses a record ('get_french_company_profile still serves its profile, with that caveat').

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