HelpMyAgent

French Company Closures

company_fr_closures

Lists French legal units entering a closed Sirene administrative period during a requested date window, while preserving their current status if later reactivated. Use when: You need French legal units whose Sirene administrative status changed to closed during a date window. Avoid when: You need BODACC deregistration notices rather than Sirene administrative cessation; use company/fr/events. Limitations: A Sirene administrative cessation is not equivalent to insolvency, liquidation or a BODACC deregistration notice. A legal unit may later be reactivated. A cursor is bound to its date-window query and should only be reused to continue that same query. 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
`limit`	No	Maximum results to return, up to 100
`since`	No	Inclusive start date; defaults to a 7-day window
`until`	No	Inclusive end date; defaults to today
`cursor`	No	Opaque Sirene cursor from next_cursor; omit it on the first call	*

Output Schema

TableJSON Schema

Name	Required	Description
`limit`	Yes	Structured value returned for “limit” as defined by this API contract.
`since`	Yes	Structured value returned for “since” as defined by this API contract.
`until`	Yes	Structured value returned for “until” as defined by this API contract.
`cursor`	Yes	Structured value returned for “cursor” as defined by this API contract.
`closures`	Yes	Structured value returned for “closures” as defined by this API contract.
`truncated`	Yes	Whether additional matching records existed beyond the returned result limit.
`limitations`	No	Known interpretation, source-coverage or freshness limitations for this result.
`next_cursor`	Yes	Structured value returned for “next cursor” as defined by this API contract.
`total_count`	Yes	Total number of matching records reported by the source or endpoint.
`returned_count`	Yes	Number of records included in this response.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 16, 2026

changedOutput schema / required

Previous value: -[
-  "since",
-  "until",
-  "cursor",
-  "next_cursor",
-  "limit",
-  "total_count",
-  "returned_count",
-  "truncated",
-  "closures",
-  "limitations"
-]New value: +[
+  "since",
+  "until",
+  "cursor",
+  "next_cursor",
+  "limit",
+  "total_count",
+  "returned_count",
+  "truncated",
+  "closures"
+]

AddedSep 9, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations provide only coarse hints, so the description adds valuable behavior: successful calls can consume an x402 payment, source records are not modified, the payment challenge is free, repeated invocation may require new payment, and cursors are bound to their original query. No contradiction with 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.

Conciseness5/5

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

Front-loaded with purpose, then organized into use/avoid, limitations, price, paid-call behavior, and accepted networks. No unnecessary fluff; every section adds actionable information and is 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?

Covers the tool's purpose, selection criteria, limitations, payment side effects, cursor constraints, and accepted networks. Output schema covers return fields, and since there are no required params, callers can rely on documented defaults. Nothing essential is missing.

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%, so the baseline is 3. The description adds useful cursor semantics—'A cursor is bound to its date-window query and should only be reused to continue that same query'—which goes beyond the schema's generic cursor description.

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 and resource: 'Lists French legal units entering a closed Sirene administrative period during a requested date window.' It also clarifies the nuanced preservation of current status if later reactivated, and explicitly distinguishes itself from BODACC/company/fr/events.

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' sections, names the alternative tool company/fr/events, and explains that Sirene administrative cessation is not equivalent to insolvency, liquidation, or BODACC deregistration. This gives an agent clear routing guidance.

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?