Skip to main content
Glama
Sirenic MCP server

Sirenic MCP server

Official

French sector benchmarks (NAF)

get_french_sector_benchmarks
Read-only

Retrieve French sector benchmarks by NAF code—active company counts, median age, workforce, revenue, margins and debt ratio—to compare a business with peers.

Instructions

Sector benchmarks and sector statistics for a French NAF activity code (any level: 68, 68.2, 68.20, 68.20B): number of active companies, median company age (+quartiles), workforce-bracket distribution, and, when at least 5 companies file public accounts, median revenue, EBITDA margin, pre-tax result and debt ratio. Peer comparison: place a company against its peers. Aggregates only, no personal data. Paid via x402 ($0.05 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": {
      "code_naf": "<code_naf>"
    },
    "name": "get_french_sector_benchmarks"
  }
}

Input Schema

NameRequiredDescriptionDefault
code_nafYesNAF rev. 2 activity code, any level (68, 68.2, 68.20, 68.20B): 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)

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

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

Beyond readOnlyHint/openWorldHint it discloses the suppression rule (financial metrics only when at least 5 companies file public accounts), the no-personal-data guarantee, the x402 price of $0.05 in USDC or EURC, and that invalid codes return 400 without being charged. These are exactly the operational facts an agent needs before spending money on a call.

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?

Information is front-loaded: the returned fields come first, then peer-comparison use, then the caveats on privacy, price and citation. The single long sentence with several parentheticals is dense but nearly every clause carries actionable content; a break into two or three sentences would improve scannability.

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, read-only aggregate tool with an output schema already present, the description covers the remaining gaps: data granularity, the minimum-sample condition for financials, privacy posture, pricing, error behavior and citation obligation. Nothing material is left for the agent to guess.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the parameter already documents the NAF rev. 2 pattern and rejection cases, so the baseline would be 3. The description nevertheless reinforces the accepted hierarchy levels (68, 68.2, 68.20, 68.20B), tying the parameter directly to the granularity of the returned aggregates, which adds modest but real meaning.

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 states a concrete resource (NAF sector benchmarks) with an exhaustive enumeration of what is returned: company counts, median age with quartiles, workforce-bracket distribution, and conditional financial metrics. It also implicitly separates itself from the company-level siblings by stressing that these are aggregates, so an agent can distinguish it from get_french_company_financials or get_french_company_profile 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 Guidelines4/5

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

The phrase 'Peer comparison: place a company against its peers' gives a clear use context, and the citation instruction sets an expectation for reporting. It never names an alternative sibling or states when *not* to use it (e.g. for a single company's own figures), so routing still requires some inference.

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