Skip to main content
Glama
Sirenic MCP server

Sirenic MCP server

Official

French company profile (SIREN)

get_french_company_profile
Read-only

Retrieve a French company’s official profile by SIREN from INSEE Sirene/INPI RNE—legal identity, address, NAF, workforce, officers, VAT, and LEI group data—for KYB and due diligence.

Instructions

Full official company profile of a French company by SIREN, from the French company registry (INSEE Sirene / INPI RNE): legal name, legal form, head office, NAF code (with its nomenclature, NAF 2025 code and status: GET /v1/lecture), workforce, officers, collective agreements (conventions_collectives, with conventions_collectives_notes reading out technical IDCC codes: 9999 means no collective agreement is assigned, it is not an agreement number to look up), VAT number, plus groupe_lei for LEI holders: the GLEIF level-2 group, direct and ultimate CONSOLIDATING parents (named, except a parent that GLEIF flags as a natural person or of an ambiguous legal form: mere_omise gives the reason, no name, no LEI; non_servie, a neutral value, when another reason leaves it out) or the declared reason for having none (accounting consolidation, never capital ownership or beneficial owners; sans_objet without a LEI). The core company data lookup for KYB and due diligence on France. An identity whose administrative status or legal category is missing in Sirene is served with blocs_absents (raison identite_incomplete) and a partial provenance. Partial diffusion (rule diffusion_partielle_nom_retenu_et_compte): a unit not proven to be a legal person is served with denomination null, counted in ecartes.diffusion_partielle. Paid via x402 ($0.005 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_profile"
  }
}

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

A3.9/5.0
Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint, so the description carries the real behavioral load and does add key facts: the call is paid via x402 ($0.005 in USDC or EURC) and results must be cited verbatim. It also discloses important edge-case semantics — blocs_absents when Sirene lacks status, partial diffusion yielding a null denomination, and sentinel values like 9999 and mere_omise. It does not cover failure modes or latency, but the payment and degradation behavior are genuinely beyond the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The opening clause is well front-loaded, but the rest is one enormous sentence with deeply nested parentheticals about GLEIF consolidating parents, mere_omise, non_servie, sans_objet and diffusion_partielle. Much of that is per-field output semantics that the existing output schema should govern, so it bloats the definition and makes it hard to parse.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given an output schema exists, the description already goes beyond what is required by covering billing, citation obligation, missing-block behavior and partial diffusion. It is complete enough for an agent to call this correctly; remaining gaps are peripheral (error/retry behavior, whether one SIREN per call).

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 parameter with 100% schema description coverage including a 9-digit pattern, so the schema already fully specifies it. The description only reinforces 'by SIREN' and adds no format, normalization, or invalid-input guidance beyond 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?

The description names a specific verb and resource ('Full official company profile of a French company by SIREN, from the French company registry') and enumerates the content surface (legal name, legal form, NAF, workforce, officers, VAT, GLEIF parents). 'The core company data lookup for KYB and due diligence on France' positions it against the many sibling endpoints (briefing, kyb_file, financials) without needing to open their schemas.

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

Usage Guidelines4/5

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

It gives a clear use context — KYB and due diligence on France, core company data lookup — which tells an agent when this is the right entry point. It stops short of explicit exclusions or named alternatives (e.g. 'for a summary use get_french_company_briefing'), so the routing is implied rather than stated.

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