Skip to main content
Glama
Sign In

HelpMyAgent

by io.github.helpmyagent
OverviewDiscussionsAdmin

French Supplier Verification

company_fr_supplier_verification

Combines public company, compliance and optional VAT/IBAN consistency checks into a supplier review result. Use when: Review a French supplier before onboarding or payment. You need a compact pre-onboarding or pre-payment review of a French supplier using public company/compliance data plus optional VAT and IBAN checks. You want one normalized supplier verdict while retaining the individual check results. Avoid when: You need a broader multi-section company dossier; use company/fr/intelligence. You only need to compare invoice identifiers and VAT information; use company/fr/invoice-check. Limitations: IBAN validation is structural and does not prove bank-account ownership by the supplier. The result is public-data decision support, not a guarantee that a supplier or payment is fraud-free. Price: 0.050 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.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "identifier": "<identifier>"
    },
    "name": "company_fr_supplier_verification"
  }
}

Input Schema

NameRequiredDescriptionDefault
ibanNoIBAN supplied for structural validation or supplier consistency checks.
identifierYesFrench company identifier: 9-digit SIREN or 14-digit SIRET.
vat_numberNoOptional or required VAT identifier used by this validation or consistency check.

Output 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.
verdictYesNormalized endpoint conclusion derived from the checked public data.
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / required
      Previous value: -[
-  "identifier",
-  "siren",
-  "name",
-  "verdict",
-  "checks",
-  "checked_at",
-  "limitations"
-]New value: +[
+  "identifier",
+  "siren",
+  "name",
+  "verdict",
+  "checks",
+  "checked_at"
+]
  2. Changed12 schema fields changed
    • addedInput schema / description
      Added value: +"Structured input parameters for the company/fr/supplier-verification API."
    • addedInput schema / properties / iban / description
      Added value: +"IBAN supplied for structural validation or supplier consistency checks."
    • addedInput schema / properties / identifier / description
      Added value: +"French company identifier: 9-digit SIREN or 14-digit SIRET."
    • addedInput schema / properties / vat_number / description
      Added value: +"Optional or required VAT identifier used by this validation or consistency check."
    • addedOutput schema / description
      Added value: +"Structured result returned by the company/fr/supplier-verification 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 / 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 / siren / description
      Added value: +"Normalized 9-digit French SIREN when available."
    • addedOutput schema / properties / verdict / description
      Added value: +"Normalized endpoint conclusion derived from the checked public data."
  3. Added

TDQS

A4.9/5.0
Behavior5/5

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

With all annotations false, the description carries the burden. It discloses source records not modified, paid-call behavior and payment consumption, non-idempotent repeat behavior, IBAN structural validation limitation, and decision-support not guarantee. No contradiction with 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?

Purpose is front-loaded, then Use/Avoid/Limitations/Price/Paid-call behavior/Networks are clearly labeled. Each sentence adds operational value; no filler.

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 multi-check tool, the description covers selection, exclusions, limitations, payment behavior, accepted networks, and expected result shape (one normalized verdict plus individual check results), while output schema covers return details.

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 already documents all three parameters with 100% coverage. Description adds context that VAT/IBAN are optional and used for consistency checks, and clarifies IBAN validation is structural, complementing the schema's per-field descriptions.

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 composite action (combines public company, compliance, and optional VAT/IBAN checks into a supplier review result), names the target resource (French supplier), and explicitly differentiates from company/fr/intelligence and company/fr/invoice-check.

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 with concrete scenarios (pre-onboarding/pre-payment review) and names alternatives (company/fr/intelligence, company/fr/invoice-check), leaving no ambiguity about tool selection.

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