HelpMyAgent

French Company Sector Statistics

company_fr_sector_statistics

Returns the source-reported active-company count for a French NAF activity plus explicit descriptive samples for age, workforce bands and optional financials; large counts can be capped at 10,000 by the source. Use when: Measure the source-reported active-company count for a French NAF activity and obtain descriptive sample statistics. Avoid when: You need an official INSEE statistical publication rather than statistics computed from company records. Limitations: The Recherche d'entreprises search engine caps large total-result counts at 10,000. When total_active is 10000, total_active_is_exact is false and the true count is at least 10,000. Age, workforce-band and financial distributions remain explicitly sampled. When the total count is capped, sample_coverage_percent is an upper bound. Price: 0.020 USD per call via x402. Paid-call behavior: source records are not modified, but a successful invocation can consume the advertised x402 payment; the payment-required challenge is free, and repeating the tool after a completed paid invocation may require a new payment. Accepted x402 networks: eip155:8453, xrpl:0.

Input Schema

TableJSON Schema

Name	Required	Description
`region`	No	Optional French region code used to restrict results geographically.
`department`	No	Optional French department code used to restrict results geographically.
`activity_code`	Yes	French NAF activity code to summarize, in the form 00.00A.
`include_financials`	No	When true, include the supported public financial sample in the sector statistics. (default false).

Output Schema

TableJSON Schema

Name	Required	Description
`region`	Yes	Structured value returned for “region” as defined by this API contract.
`age_years`	Yes	Structured value returned for “age years” as defined by this API contract.
`department`	Yes	Structured value returned for “department” as defined by this API contract.
`limitations`	No	Known interpretation, source-coverage or freshness limitations for this result.
`generated_at`	Yes	UTC timestamp at which this derived result was generated.
`sample_limit`	Yes	Structured value returned for “sample limit” as defined by this API contract.
`total_active`	Yes	Structured value returned for “total active” as defined by this API contract.
`activity_code`	Yes	Structured value returned for “activity code” as defined by this API contract.
`sampled_count`	Yes	Structured value returned for “sampled count” as defined by this API contract.
`median_revenue`	Yes	Structured value returned for “median revenue” as defined by this API contract.
`median_net_income`	Yes	Structured value returned for “median net income” as defined by this API contract.
`total_active_is_exact`	Yes	Structured value returned for “total active is exact” as defined by this API contract.
`financial_sample_count`	Yes	Structured value returned for “financial sample count” as defined by this API contract.
`sample_coverage_percent`	Yes	Structured value returned for “sample coverage percent” as defined by this API contract.
`employee_band_distribution`	Yes	Structured value returned for “employee band distribution” as defined by this API contract.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 16, 2026

changedOutput schema / required

Previous value: -[
-  "activity_code",
-  "department",
-  "region",
-  "total_active",
-  "total_active_is_exact",
-  "sampled_count",
-  "sample_limit",
-  "sample_coverage_percent",
-  "age_years",
-  "employee_band_distribution",
-  "financial_sample_count",
-  "median_revenue",
-  "median_net_income",
-  "generated_at",
-  "limitations"
-]New value: +[
+  "activity_code",
+  "department",
+  "region",
+  "total_active",
+  "total_active_is_exact",
+  "sampled_count",
+  "sample_limit",
+  "sample_coverage_percent",
+  "age_years",
+  "employee_band_distribution",
+  "financial_sample_count",
+  "median_revenue",
+  "median_net_income",
+  "generated_at"
+]

Changed4 schema fields changedSep 9, 2026

addedOutput schema / properties / sample_coverage_percent

Added value: +{
+  "description": "Structured value returned for “sample coverage percent” as defined by this API contract.",
+  "type": "number"
+}

addedOutput schema / properties / sample_limit

Added value: +{
+  "description": "Structured value returned for “sample limit” as defined by this API contract.",
+  "type": "integer"
+}

addedOutput schema / properties / total_active_is_exact

Added value: +{
+  "description": "Structured value returned for “total active is exact” as defined by this API contract.",
+  "type": "boolean"
+}

changedOutput schema / required

Previous value: -[
-  "activity_code",
-  "department",
-  "region",
-  "total_active",
-  "sampled_count",
-  "age_years",
-  "employee_band_distribution",
-  "financial_sample_count",
-  "median_revenue",
-  "median_net_income",
-  "generated_at",
-  "limitations"
-]New value: +[
+  "activity_code",
+  "department",
+  "region",
+  "total_active",
+  "total_active_is_exact",
+  "sampled_count",
+  "sample_limit",
+  "sample_coverage_percent",
+  "age_years",
+  "employee_band_distribution",
+  "financial_sample_count",
+  "median_revenue",
+  "median_net_income",
+  "generated_at",
+  "limitations"
+]

Changed23 schema fields changedSep 8, 2026

addedInput schema / description

Added value: +"Structured input parameters for the company/fr/sector-statistics API."

addedInput schema / properties / activity_code / description

Added value: +"French NAF activity code to summarize, in the form 00.00A."

addedInput schema / properties / department / description

Added value: +"Optional French department code used to restrict results geographically."

addedInput schema / properties / include_financials / description

Added value: +"When true, include the supported public financial sample in the sector statistics. (default false)."

addedInput schema / properties / region / description

Added value: +"Optional French region code used to restrict results geographically."

addedOutput schema / description

Added value: +"Structured result returned by the company/fr/sector-statistics API."

addedOutput schema / properties / activity_code / description

Added value: +"Structured value returned for “activity code” as defined by this API contract."

addedOutput schema / properties / age_years / description

Added value: +"Structured value returned for “age years” as defined by this API contract."

addedOutput schema / properties / age_years / properties / max / description

Added value: +"Structured value returned for “max” as defined by this API contract."

addedOutput schema / properties / age_years / properties / median / description

Added value: +"Structured value returned for “median” as defined by this API contract."

addedOutput schema / properties / age_years / properties / min / description

Added value: +"Structured value returned for “min” as defined by this API contract."

addedOutput schema / properties / department / description

Added value: +"Structured value returned for “department” as defined by this API contract."

addedOutput schema / properties / employee_band_distribution / description

Added value: +"Structured value returned for “employee band distribution” as defined by this API contract."

addedOutput schema / properties / employee_band_distribution / items / properties / code / description
```
Added value: +"Structured value returned for “code” as defined by this API contract."
```
addedOutput schema / properties / employee_band_distribution / items / properties / count / description
```
Added value: +"Structured value returned for “count” as defined by this API contract."
```

addedOutput schema / properties / financial_sample_count / description

Added value: +"Structured value returned for “financial sample count” as defined by this API contract."

addedOutput schema / properties / generated_at / description

Added value: +"UTC timestamp at which this derived result was generated."

addedOutput schema / properties / limitations / description

Added value: +"Known interpretation, source-coverage or freshness limitations for this result."

addedOutput schema / properties / median_net_income / description

Added value: +"Structured value returned for “median net income” as defined by this API contract."

addedOutput schema / properties / median_revenue / description

Added value: +"Structured value returned for “median revenue” as defined by this API contract."

addedOutput schema / properties / region / description

Added value: +"Structured value returned for “region” as defined by this API contract."

addedOutput schema / properties / sampled_count / description

Added value: +"Structured value returned for “sampled count” as defined by this API contract."

addedOutput schema / properties / total_active / description

Added value: +"Structured value returned for “total active” as defined by this API contract."

AddedSep 6, 2026

TDQS

A4.7/5.0

Behavior5/5

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

The description goes well beyond annotations by disclosing the 10,000 cap, the exactness flag behavior, sample_coverage_percent semantics, pricing, paid-call behavior, and accepted networks. It also clarifies that source records are not modified, which is especially useful given readOnlyHint is false.

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?

The description is well-structured with labeled sections, front-loads the core behavior, and keeps each sentence purposeful. While it contains more detail than average, every sentence addresses a practical concern such as pricing, limitations, or usage boundaries.

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?

The description covers the tool's purpose, usage boundaries, limitations, output semantics (via cap/exactness/sample coverage), pricing, and payment behavior. An output schema exists, so not describing return fields is acceptable. Nothing essential for correct selection or invocation is missing.

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 documents all four parameters. The description adds minimal parameter-level detail, mostly echoing the activity code and optional financials without expanding on format or behavior 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 clearly states a specific verb ('Returns') and resource: the source-reported active-company count for a French NAF activity, plus descriptive samples. It distinguishes itself from sibling tools by focusing on sector statistics rather than company profiles, benchmarks, or financials.

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?

The description provides explicit 'Use when' and 'Avoid when' guidance, including a concrete alternative context (official INSEE publication vs. computed company records). This leaves no ambiguity about when the tool should be selected.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All HelpMyAgent tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?