Skip to main content
Glama

HelpMyAgent

by io.github.helpmyagent
OverviewDiscussionsAdmin

French Financial Regulatory Approvals

company_fr_regulatory_approvals

Checks a French company against the public REGAFI register and normalizes matching regulatory records. Use when: Check whether a French company appears in the public REGAFI register. You need to know whether a French company appears in the public REGAFI register and inspect normalized matching records. You specifically need financial-regulatory registration signals rather than general company compliance. Avoid when: You want public alerts plus a REGAFI registration summary; use company/fr/compliance. You need general sanctions or asset-freeze screening; use company/fr/compliance. Limitations: Coverage is limited to the public REGAFI source used by the endpoint. No REGAFI match is not a universal statement that an entity is unregulated in every jurisdiction or activity. 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
NameRequiredDescriptionDefault
identifierYesFrench company identifier: 9-digit SIREN or 14-digit SIRET.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesPublicly available company, person, buyer or record name for this result.
sirenYesNormalized 9-digit French SIREN when available.
existsYesWhether the requested company or public record was found in the checked source.
approvalsYesStructured value returned for “approvals” as defined by this API contract.
regulatedYesStructured value returned for “regulated” as defined by this API contract.
checked_atYesUTC timestamp at which HelpMyAgent performed the check.
identifierYesIdentifier supplied for the request, echoed in normalized form when applicable.
limitationsNoKnown interpretation, source-coverage or freshness limitations for this result.
source_statusYesAvailability status of the relevant upstream public source. (allowed values: ok, unavailable, not_queried).
approval_countYesStructured value returned for “approval count” as defined by this API contract.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / required
      Previous value: -[
-  "identifier",
-  "exists",
-  "siren",
-  "name",
-  "source_status",
-  "regulated",
-  "approval_count",
-  "approvals",
-  "checked_at",
-  "limitations"
-]New value: +[
+  "identifier",
+  "exists",
+  "siren",
+  "name",
+  "source_status",
+  "regulated",
+  "approval_count",
+  "approvals",
+  "checked_at"
+]
  2. Changed20 schema fields changed
    • addedInput schema / description
      Added value: +"Structured input parameters for the company/fr/regulatory-approvals 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/regulatory-approvals API."
    • addedOutput schema / properties / approval_count / description
      Added value: +"Structured value returned for “approval count” as defined by this API contract."
    • addedOutput schema / properties / approvals / description
      Added value: +"Structured value returned for “approvals” as defined by this API contract."
    • addedOutput schema / properties / approvals / items / properties / activities / description
      Added value: +"Structured value returned for “activities” as defined by this API contract."
    • addedOutput schema / properties / approvals / items / properties / category / description
      Added value: +"Structured value returned for “category” as defined by this API contract."
    • addedOutput schema / properties / approvals / items / properties / cib / description
      Added value: +"Structured value returned for “cib” as defined by this API contract."
    • addedOutput schema / properties / approvals / items / properties / lei / description
      Added value: +"Structured value returned for “lei” as defined by this API contract."
    • addedOutput schema / properties / approvals / items / properties / name / description
      Added value: +"Publicly available company, person, buyer or record name for this result."
    • addedOutput schema / properties / approvals / items / properties / siren / description
      Added value: +"Normalized 9-digit French SIREN when available."
    • addedOutput schema / properties / approvals / items / properties / status / description
      Added value: +"Normalized endpoint or source status."
    • addedOutput schema / properties / checked_at / description
      Added value: +"UTC timestamp at which HelpMyAgent performed the check."
    • addedOutput schema / properties / exists / description
      Added value: +"Whether the requested company or public record was found in the checked source."
    • addedOutput schema / properties / identifier / description
      Added value: +"Identifier supplied for the request, echoed in normalized form when applicable."
    • 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 / regulated / description
      Added value: +"Structured value returned for “regulated” as defined by this API contract."
    • 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)."
  3. Added

TDQS

A4.6/5.0
Behavior5/5

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

The description substantially expands beyond the sparse annotations. It discloses that source records are not modified, that a successful paid invocation can consume x402 payment, that the payment challenge is free, and that repeating the tool may require a new payment. It also explains REGAFI coverage limitations, which is important for interpreting a no-match result.

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?

The description is organized into clear labeled sections and front-loads the core purpose. There is some redundancy between the opening sentence and the 'Use when' section, but the additional details on limitations, pricing, and payment behavior all earn their place.

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 tool with an output schema, the description is complete. It covers when to use, when not to use, limitations, payment side effects, and accepted networks. The output schema handles return-value documentation, so nothing essential 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 coverage is 100%: the sole parameter 'identifier' is fully defined with a regex pattern and an explanation of SIREN/SIRET. The description adds little beyond 'French company,' but because the schema carries the full parameter burden, the baseline of 3 is appropriate.

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 opens with a specific verb and resource: 'Checks a French company against the public REGAFI register and normalizes matching regulatory records.' It clearly distinguishes this tool from company/fr/compliance by framing it as financial-regulatory registration signals rather than general compliance, so an agent can differentiate it from siblings.

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 'Use when' and 'Avoid when' sections give explicit decision criteria. It states to use this tool when checking REGAFI registration and explicitly routes alternatives to company/fr/compliance for public alerts plus REGAFI summary or sanctions/asset-freeze screening. This is unambiguous 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 toolsInspect
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