Skip to main content
Glama

HelpMyAgent

by io.github.helpmyagent
OverviewDiscussionsAdmin

French Company Compliance Checks

company_fr_compliance

Checks a French company against supported public alert and sanctions sources and adds a structured REGAFI registration summary. The absence of a match must not be interpreted as a guarantee of compliance. Use when: You need to check a French company against the supported public AMF alert and national asset-freeze sources. You need a structured REGAFI registration summary together with public alert and sanctions checks. Avoid when: You need a complete AML/KYC decision, beneficial-owner screening or a legal guarantee of compliance. You need company insolvency or deregistration risk rather than sanctions/alert screening; use company/fr/risk. Limitations: NO_PUBLIC_ALERT_FOUND means only that no match was found in the checked public sources; it is not a compliance guarantee. Matches without a shared administrative identifier can be inferred and are explicitly marked with confidence; an input domain is checked as a separate subject. 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
domainNoOptional domain to check separately; it is not considered officially associated with the company
identifierYes9-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.
checksYesStructured value returned for “checks” as defined by this API contract.
domainYesStructured value returned for “domain” as defined by this API contract.
existsYesWhether the requested company or public record was found in the checked source.
statusYesNormalized endpoint or source status. (allowed values: PUBLIC_ALERT_FOUND, NO_PUBLIC_ALERT_FOUND, INCOMPLETE, COMPANY_NOT_FOUND).
matchesYesCandidate public-list or source matches returned by the endpoint.
checked_atYesUTC timestamp at which HelpMyAgent performed the check.
identifierYesIdentifier supplied for the request, echoed in normalized form when applicable.
regulatoryNoStructured value returned for “regulatory” as defined by this API contract.
limitationsNoKnown interpretation, source-coverage or freshness limitations for this result.
company_statusYesCurrent public administrative company status when available.
identifier_typeYesNormalized identifier type, such as SIREN or SIRET when applicable. (allowed values: siren, siret).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / regulatory
      Added value: +{
+  "description": "Structured value returned for “regulatory” as defined by this API contract.",
+  "properties": {
+    "approval_count": {
+      "description": "Structured value returned for “approval count” as defined by this API contract.",
+      "type": [
+        "integer",
+        "null"
+      ]
+    },
+    "regulated": {
+      "description": "Structured value returned for “regulated” as defined by this API contract.",
+      "type": [
+        "boolean",
+        "null"
+      ]
+    },
+    "source_status": {
+      "description": "Availability status of the relevant upstream public source. (allowed values: ok, unavailable, not_queried).",
+      "enum": [
+        "ok",
+        "unavailable",
+        "not_queried"
+      ],
+      "type": "string"
+    }
+  },
+  "required": [
+    "source_status",
+    "regulated",
+    "approval_count"
+  ],
+  "type": "object"
+}
  2. Changed1 schema field changed
    • changedOutput schema / required
      Previous value: -[
-  "identifier",
-  "identifier_type",
-  "exists",
-  "siren",
-  "name",
-  "company_status",
-  "domain",
-  "status",
-  "checked_at",
-  "checks",
-  "matches",
-  "limitations"
-]New value: +[
+  "identifier",
+  "identifier_type",
+  "exists",
+  "siren",
+  "name",
+  "company_status",
+  "domain",
+  "status",
+  "checked_at",
+  "checks",
+  "matches"
+]
  3. Changed30 schema fields changed
    • addedInput schema / description
      Added value: +"Structured input parameters for the company/fr/compliance API."
    • addedOutput schema / description
      Added value: +"Structured result returned by the company/fr/compliance API."
    • addedOutput schema / properties / checked_at / description
      Added value: +"UTC timestamp at which HelpMyAgent performed the check."
    • addedOutput schema / properties / checks / description
      Added value: +"Structured value returned for “checks” as defined by this API contract."
    • addedOutput schema / properties / checks / items / properties / check / description
      Added value: +"Structured value returned for “check” as defined by this API contract."
    • addedOutput schema / properties / checks / items / properties / limitation / description
      Added value: +"Structured value returned for “limitation” as defined by this API contract."
    • addedOutput schema / properties / checks / items / properties / match_count / description
      Added value: +"Number of candidate matches returned by the screening operation."
    • addedOutput schema / properties / checks / items / properties / publication_date / description
      Added value: +"Structured value returned for “publication date” as defined by this API contract."
    • addedOutput schema / properties / checks / items / properties / source / description
      Added value: +"Structured value returned for “source” as defined by this API contract."
    • addedOutput schema / properties / checks / items / properties / source_records / description
      Added value: +"Structured value returned for “source records” as defined by this API contract."
    • addedOutput schema / properties / checks / items / properties / source_type / description
      Added value: +"Structured value returned for “source type” as defined by this API contract."
    • addedOutput schema / properties / checks / items / properties / status / description
      Added value: +"Normalized endpoint or source status. (allowed values: ok, unavailable, not_queried)."
    • addedOutput schema / properties / company_status / description
      Added value: +"Current public administrative company status when available."
    • addedOutput schema / properties / domain / description
      Added value: +"Structured value returned for “domain” as defined by this API contract."
    • 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 / identifier_type / description
      Added value: +"Normalized identifier type, such as SIREN or SIRET when applicable. (allowed values: siren, siret)."
    • addedOutput schema / properties / limitations / description
      Added value: +"Known interpretation, source-coverage or freshness limitations for this result."
    • addedOutput schema / properties / matches / description
      Added value: +"Candidate public-list or source matches returned by the endpoint."
    • addedOutput schema / properties / matches / items / properties / check / description
      Added value: +"Structured value returned for “check” as defined by this API contract."
    • addedOutput schema / properties / matches / items / properties / confidence / description
      Added value: +"Confidence indicator associated with an inferred or derived result."
    • addedOutput schema / properties / matches / items / properties / match_method / description
      Added value: +"Structured value returned for “match method” as defined by this API contract."
    • addedOutput schema / properties / matches / items / properties / match_source_type / description
      Added value: +"Structured value returned for “match source type” as defined by this API contract. (allowed values: SOURCE_PUBLIQUE, INFERE)."
    • addedOutput schema / properties / matches / items / properties / name / description
      Added value: +"Publicly available company, person, buyer or record name for this result."
    • addedOutput schema / properties / matches / items / properties / source / description
      Added value: +"Structured value returned for “source” as defined by this API contract."
    • addedOutput schema / properties / matches / items / properties / source_type / description
      Added value: +"Structured value returned for “source type” as defined by this API contract."
    • addedOutput schema / properties / matches / items / properties / subject / description
      Added value: +"Structured value returned for “subject” as defined by this API contract. (allowed values: company_identity, domain_input)."
    • 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 / status / description
      Added value: +"Normalized endpoint or source status. (allowed values: PUBLIC_ALERT_FOUND, NO_PUBLIC_ALERT_FOUND, INCOMPLETE, COMPANY_NOT_FOUND)."
  4. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the annotations, the description discloses paid-call behavior, the free payment challenge, the possibility of needing a new payment on repeat invocation, and the fact that source records are not modified. It also warns that absence of a match is not a compliance guarantee and that inferred matches are marked with confidence. No statement contradicts 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?

The description is longer than average but every section earns its place: purpose, routing, limitations, pricing, paid-call behavior, and accepted networks. It is front-loaded with the core function and the key compliance disclaimer.

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 paid compliance tool, the description covers operational, financial, and data-quality context completely: when to use, what not to conclude, payment specifics, and supported networks. With an output schema present, return-value details do not need to be restated.

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?

The schema already covers both parameters, so the description correctly avoids repeating formats. It adds useful semantic context by noting that the domain is checked as a separate, non-officially-associated subject and that matches without a shared administrative identifier are inferred with explicit confidence.

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 specific operation—checking a French company against supported public alert and sanctions sources—and adds the structured REGAFI registration summary as a distinct output. It distinguishes itself from siblings by naming the exact scope and by explicitly contrasting with company/fr/risk.

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 routing criteria, including when to choose company/fr/risk instead. It also excludes complete AML/KYC decisions, beneficial-owner screening, legal guarantees, and insolvency/deregistration risk, leaving no ambiguity about alternatives.

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