HelpMyAgent

French Industrial Installation Risk

company_fr_industrial_risk

Finds public ICPE, Seveso and IED installation signals across the company establishments available from SIRENE, with explicit coverage indicators. Use when: Find public ICPE, Seveso and IED installation signals across the known establishments of a French company. Avoid when: You only need the company establishment list; use company/fr/establishments. Limitations: Coverage is explicit and can be partial for very large companies or when public sources are unavailable. Price: 0.010 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	Default
`identifier`	Yes	French company identifier: 9-digit SIREN or 14-digit SIRET.

Output Schema

TableJSON Schema

Name	Required	Description
`name`	Yes	Publicly available company, person, buyer or record name for this result.
`siren`	Yes	Normalized 9-digit French SIREN when available.
`exists`	Yes	Whether the requested company or public record was found in the checked source.
`checked_at`	Yes	UTC timestamp at which HelpMyAgent performed the check.
`identifier`	Yes	Identifier supplied for the request, echoed in normalized form when applicable.
`limitations`	No	Known interpretation, source-coverage or freshness limitations for this result.
`installations`	Yes	Structured value returned for “installations” as defined by this API contract.
`source_status`	Yes	Availability status of the relevant upstream public source. (allowed values: ok, partial, unavailable, not_queried).
`communes_total`	Yes	Structured value returned for “communes total” as defined by this API contract.
`communes_scanned`	Yes	Structured value returned for “communes scanned” as defined by this API contract.
`coverage_complete`	Yes	Whether the checked public-source coverage was sufficient for the endpoint’s stated scope.
`installation_count`	Yes	Structured value returned for “installation count” as defined by this API contract.
`establishments_total`	Yes	Structured value returned for “establishments total” as defined by this API contract.
`establishments_scanned`	Yes	Structured value returned for “establishments scanned” as defined by this API contract.
`headquarters_commune_code`	Yes	Structured value returned for “headquarters commune code” 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: -[
-  "identifier",
-  "exists",
-  "siren",
-  "name",
-  "headquarters_commune_code",
-  "source_status",
-  "establishments_total",
-  "establishments_scanned",
-  "communes_total",
-  "communes_scanned",
-  "installation_count",
-  "installations",
-  "coverage_complete",
-  "checked_at",
-  "limitations"
-]New value: +[
+  "identifier",
+  "exists",
+  "siren",
+  "name",
+  "headquarters_commune_code",
+  "source_status",
+  "establishments_total",
+  "establishments_scanned",
+  "communes_total",
+  "communes_scanned",
+  "installation_count",
+  "installations",
+  "coverage_complete",
+  "checked_at"
+]

Changed7 schema fields changedSep 9, 2026

addedOutput schema / properties / communes_scanned

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

addedOutput schema / properties / communes_total

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

addedOutput schema / properties / establishments_scanned

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

addedOutput schema / properties / establishments_total

Added value: +{
+  "description": "Structured value returned for “establishments total” as defined by this API contract.",
+  "type": [
+    "integer",
+    "null"
+  ]
+}

changedOutput schema / properties / source_status / description

Previous value: -"Availability status of the relevant upstream public source. (allowed values: ok, unavailable, not_queried)."New value: +"Availability status of the relevant upstream public source. (allowed values: ok, partial, unavailable, not_queried)."

changedOutput schema / properties / source_status / enum

Previous value: -[
-  "ok",
-  "unavailable",
-  "not_queried"
-]New value: +[
+  "ok",
+  "partial",
+  "unavailable",
+  "not_queried"
+]

changedOutput schema / required

Previous value: -[
-  "identifier",
-  "exists",
-  "siren",
-  "name",
-  "headquarters_commune_code",
-  "source_status",
-  "installation_count",
-  "installations",
-  "coverage_complete",
-  "checked_at",
-  "limitations"
-]New value: +[
+  "identifier",
+  "exists",
+  "siren",
+  "name",
+  "headquarters_commune_code",
+  "source_status",
+  "establishments_total",
+  "establishments_scanned",
+  "communes_total",
+  "communes_scanned",
+  "installation_count",
+  "installations",
+  "coverage_complete",
+  "checked_at",
+  "limitations"
+]

Changed23 schema fields changedSep 8, 2026

addedInput schema / description

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

addedInput schema / properties / identifier / description

Added value: +"French company identifier: 9-digit SIREN or 14-digit SIRET."

addedOutput schema / description

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

addedOutput schema / properties / checked_at / description

Added value: +"UTC timestamp at which HelpMyAgent performed the check."

addedOutput schema / properties / coverage_complete / description

Added value: +"Whether the checked public-source coverage was sufficient for the endpoint’s stated scope."

addedOutput schema / properties / exists / description

Added value: +"Whether the requested company or public record was found in the checked source."

addedOutput schema / properties / headquarters_commune_code / description

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

addedOutput schema / properties / identifier / description

Added value: +"Identifier supplied for the request, echoed in normalized form when applicable."

addedOutput schema / properties / installation_count / description

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

addedOutput schema / properties / installations / description

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

addedOutput schema / properties / installations / items / properties / address / description

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

addedOutput schema / properties / installations / items / properties / city / description

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

addedOutput schema / properties / installations / items / properties / code_aiot / description

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

addedOutput schema / properties / installations / items / properties / ied / description

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

addedOutput schema / properties / installations / items / properties / name / description

Added value: +"Publicly available company, person, buyer or record name for this result."

addedOutput schema / properties / installations / items / properties / regime / description

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

addedOutput schema / properties / installations / items / properties / seveso / description

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

addedOutput schema / properties / installations / items / properties / siret / description
```
Added value: +"Normalized 14-digit French SIRET when available."
```
addedOutput schema / properties / installations / items / properties / status / description
```
Added value: +"Normalized endpoint or source status."
```

addedOutput schema / properties / limitations / description

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

addedOutput schema / properties / name / description

Added value: +"Publicly available company, person, buyer or record name for this result."

addedOutput schema / properties / siren / description

Added value: +"Normalized 9-digit French SIREN when available."

addedOutput schema / properties / source_status / description

Added value: +"Availability status of the relevant upstream public source. (allowed values: ok, unavailable, not_queried)."

AddedSep 6, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations offer no positive safety hints (all false), so the description carries the burden of behavioral disclosure. It adds valuable context: source records are not modified, paid calls consume payment, the payment-required challenge is free, and repeat calls may require new payment. This goes well beyond the bare annotation fields without contradicting them.

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?

Well-organized with labeled sections (use, avoid, limitations, price, paid behavior). The 'Use when' sentence largely restates the opening sentence, creating minor redundancy, but the structure is front-loaded and easy to scan.

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 single-parameter paid tool with an output schema, the description covers purpose, alternatives, limitations, pricing, payment semantics, and accepted networks. Nothing essential is missing for an agent to decide whether and how to invoke it.

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 identifier parameter is already fully defined with format and pattern. The description adds no new parameter-level meaning, but none is needed given the complete 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?

States a specific verb ('Finds') and a precise resource: public ICPE, Seveso, and IED installation signals across SIRENE establishments. The scope is clearly distinguished from the simpler establishment-list sibling, and the title reinforces the domain.

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?

Provides explicit 'Use when' and 'Avoid when' guidance, directly naming company/fr/establishments as the alternative. Limitations about partial coverage for large companies or unavailable public sources further help an agent decide when the tool is appropriate.

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?