Skip to main content
Glama
Sirenic MCP server

Sirenic MCP server

Official

Prospect French companies

prospect_french_companies
Read-only

Build French B2B company prospect lists filtered by NAF code, location, legal form, workforce, age, RGE certification, or gender-equality index; retrieve up to 100 active companies per paid page.

Instructions

French B2B prospecting and lead generation: build company lists over the full French registry, filtered by NAF activity code, departement/postal code, legal form, workforce, age, RGE certification, gender-equality index. Returns up to 100 active companies per page; each page is one x402 payment ($0.02 in USDC or EURC). When you report a result, cite its citation verbatim.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "prospect_french_companies"
  }
}

Input Schema

NameRequiredDescriptionDefault
nafNoNAF/APE code or prefix, at least two digits (62, 62.0, 62.01, 62.01Z): only the NAF rev. 2 form is retained (sub-class 62.01Z, and its levels: division 62, group 62.0, class 62.01); a code of an older nomenclature (NAF rev. 1: 55.3A, activity not recoded since rev. 2 came into force) is not, nor is INSEE's provisional value 00.00Z (no division 00 in NAF rev. 2); any other code is refused (400, not charged); a well-formed code absent from INSEE's official NAF rev. 2 list (732 sub-classes, and their classes, groups and divisions), nomenclature of the stock served (NAFRev2), a NAF 2025 code included (62.10Y, group 46.8), is refused as a criterion, with a 400 never charged: NAF 2025 becomes targetable from the first NAF25-coded stock, expected in February 2027
rgeNotrue = active RGE environmental certification
pageNoPage number (one payment per page)
age_maxNoMaximum company age in years
age_minNoMinimum company age in years
egapro_minNoMinimum gender-equality index (0-100) of the latest published year; a company whose latest year is not computable is excluded
code_postalNoPostal-code prefix (2-5 digits), exclusive with departement
departementNoRegistered-office departement, by postal code: 01-19, 21-95, 971-978; 2A, 2B, 984, 986-989 refused for now (400 departement_non_servi, not charged); exclusive with code_postal; a narrow read (departement=978, code_postal=20 or code_postal=97150) may for now exceed the 8 s budget and return 503 budget_depasse, not charged
effectif_maxNoMaximum workforce (number of employees)
effectif_minNoMinimum workforce (number of employees)
forme_juridiqueNoINSEE legal-category prefix, e.g. 54

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

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered; the description adds genuinely non-structured behavior: a hard cap of 100 companies per page, a metered x402 charge of $0.02 in USDC or EURC per page, and a citation obligation on reporting results. It stops short of describing what happens on failed/refused criteria or whether an unfiltered call incurs charges, which the schema covers per-parameter but not globally.

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

Conciseness5/5

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

Three sentences, front-loaded with purpose, then pagination and cost, then the citation obligation. Every clause carries operational information (filters, price, page size, citation) with no filler or repetition of the title.

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?

With 11 optional parameters, an output schema, and annotations covering the read-only profile, the description supplies the missing operational context: page size, cost per page, and citation handling. The remaining gap is that zero required parameters means an unfiltered (and non-free) call is possible, and the description gives no caution about that or about total-result bounds.

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 schema already carries the detailed semantics (NAF rev. 2 rules, departement/code_postal exclusivity, RGE, egapro computability). The description only restates the filter categories in prose, adding no syntax or constraint information beyond what the schema provides, which is the baseline case for full coverage.

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 concrete verb-and-resource statement ('build company lists over the full French registry') and enumerates the exact filter dimensions available, so the agent knows this is a filtered list-building tool rather than a single-company lookup. It never names or contrasts the closest siblings (search_french_companies, query_french_companies), so differentiation is only implicit through the 'prospecting and lead generation' framing.

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?

'Prospecting and lead generation' implies the scenario in which this tool is the right choice, and the per-page pricing hints it is for bulk enumeration rather than point lookups. However, there is no explicit when-to-use/when-not guidance and no routing to alternatives for single-company retrieval or comparison.

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