Skip to main content
Glama

HelpMyAgent

by io.github.helpmyagent
OverviewDiscussionsAdmin

Payment context for a French company

company_fr_payment_context

Returns structured public counterparty context before an automated B2B payment. It never approves or recommends a payment. Use when: Returns structured public counterparty context before an automated B2B payment. It never approves or recommends a payment. You need compact public counterparty context immediately before an automated B2B payment. You want company status, legal-risk and compliance signals together without a full KYB dossier. Avoid when: You only need existence or administrative status; use company/fr/verify. You need a broader multi-section company dossier; use company/fr/intelligence. Limitations: This endpoint supplies decision context but never approves, blocks or recommends a payment. It does not verify bank-account ownership, invoice authenticity or private payment behavior. 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 supplied as additional counterparty context; it is checked separately and is not treated as proof of company ownership.
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.
coverageYesCoverage information describing which underlying services or sources were available.
checked_atYesUTC timestamp at which HelpMyAgent performed the check.
identifierYesIdentifier supplied for the request, echoed in normalized form when applicable.
legal_riskYesStructured value returned for “legal risk” 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.
radiation_eventsYesStructured value returned for “radiation events” as defined by this API contract.
compliance_statusYesStructured value returned for “compliance status” as defined by this API contract.
public_alerts_foundYesStructured value returned for “public alerts found” as defined by this API contract.
latest_relevant_eventYesStructured value returned for “latest relevant event” as defined by this API contract.
collective_procedure_eventsYesStructured value returned for “collective procedure events” 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",
-  "identifier_type",
-  "exists",
-  "siren",
-  "name",
-  "company_status",
-  "legal_risk",
-  "compliance_status",
-  "public_alerts_found",
-  "collective_procedure_events",
-  "radiation_events",
-  "latest_relevant_event",
-  "checked_at",
-  "coverage",
-  "limitations"
-]New value: +[
+  "identifier",
+  "identifier_type",
+  "exists",
+  "siren",
+  "name",
+  "company_status",
+  "legal_risk",
+  "compliance_status",
+  "public_alerts_found",
+  "collective_procedure_events",
+  "radiation_events",
+  "latest_relevant_event",
+  "checked_at",
+  "coverage"
+]
  2. Changed19 schema fields changed
    • addedInput schema / description
      Added value: +"Structured input parameters for the company/fr/payment-context API."
    • addedInput schema / properties / domain / description
      Added value: +"Optional domain supplied as additional counterparty context; it is checked separately and is not treated as proof of company ownership."
    • 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/payment-context API."
    • addedOutput schema / properties / checked_at / description
      Added value: +"UTC timestamp at which HelpMyAgent performed the check."
    • addedOutput schema / properties / collective_procedure_events / description
      Added value: +"Structured value returned for “collective procedure events” as defined by this API contract."
    • changedOutput schema / properties / company_status
      Previous value: -[]New value: +{
+  "description": "Current public administrative company status when available."
+}
    • addedOutput schema / properties / compliance_status / description
      Added value: +"Structured value returned for “compliance status” as defined by this API contract."
    • addedOutput schema / properties / coverage / description
      Added value: +"Coverage information describing which underlying services or sources were available."
    • 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."
    • changedOutput schema / properties / latest_relevant_event
      Previous value: -[]New value: +{
+  "description": "Structured value returned for “latest relevant event” as defined by this API contract."
+}
    • changedOutput schema / properties / legal_risk
      Previous value: -[]New value: +{
+  "description": "Structured value returned for “legal risk” as defined by this API contract."
+}
    • addedOutput schema / properties / limitations / description
      Added value: +"Known interpretation, source-coverage or freshness limitations for this result."
    • changedOutput schema / properties / name
      Previous value: -[]New value: +{
+  "description": "Publicly available company, person, buyer or record name for this result."
+}
    • addedOutput schema / properties / public_alerts_found / description
      Added value: +"Structured value returned for “public alerts found” as defined by this API contract."
    • addedOutput schema / properties / radiation_events / description
      Added value: +"Structured value returned for “radiation events” as defined by this API contract."
    • changedOutput schema / properties / siren
      Previous value: -[]New value: +{
+  "description": "Normalized 9-digit French SIREN when available."
+}
  3. Added

TDQS

A4.5/5.0
Behavior5/5

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

The annotations are minimal (all false hints), so the description carries the transparency burden. It clearly discloses payment side effects, that source records are not modified, that no payment is approved/blocked/recommended, and that bank-account ownership, invoice authenticity, and private payment behavior are not verified. This is rich behavioral context beyond the structured fields.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The description is well-sectioned and front-loads the core purpose, but it repeats the sentence 'Returns structured public counterparty context before an automated B2B payment. It never approves or recommends a payment.' verbatim in the Use when section. This duplication means not every sentence earns its 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?

With an output schema present and both parameters fully documented, the description supplies the remaining operational context an agent needs: price, accepted x402 networks, paid-call behavior, limitations, and explicit sibling routing. Nothing essential for correct selection or invocation 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?

Input schema coverage is 100%, and both parameters already have meaningful descriptions (SIREN/SIRET pattern and the optional domain's non-ownership semantics). The description adds no parameter-level detail beyond what the schema provides, so 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: 'Returns structured public counterparty context before an automated B2B payment.' It further clarifies what the tool does not do ('never approves or recommends a payment') and distinguishes itself from siblings by naming verify and intelligence as alternatives for other needs.

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?

Explicit 'Use when' and 'Avoid when' sections give precise selection criteria: compact counterparty context before an automated payment, or status/risk/compliance signals without a full KYB dossier. It also names alternatives (company/fr/verify, company/fr/intelligence) for excluded cases.

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