Skip to main content
Glama

HelpMyAgent

by io.github.helpmyagent
OverviewDiscussionsAdmin

French Company Intelligence

company_fr_intelligence

Aggregates selected existing French company intelligence services into a single call, with selectable sections and tolerance for temporarily unavailable sources. Use when: You need several existing French Company intelligence sections in one agent-ready call. You want to select a combination of profile, directors, financials, events, risk, certifications, public contracts, compliance, aids, signals or opportunities. You need the former public-data KYB bundle by requesting profile, directors, financials, risk and compliance together. Avoid when: You need only one narrow datum and want the smallest, most specific response; call the dedicated endpoint directly. You require every requested section to be available; this aggregator is designed to tolerate temporarily unavailable sources and report partial coverage. Limitations: This is an aggregator of existing HelpMyAgent Company services and does not create an independent data source or additional factual coverage. Requested sections can be reported unavailable when an underlying public source or service is temporarily unavailable. 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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainNoOptional domain used by the compliance section; it is not treated as an officially verified company domain.
includeNoOptional list of existing Company sections to aggregate in the response
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.
existsYesWhether the requested company or public record was found in the checked source.
sectionsYesNamed result sections produced by this aggregator.
checked_atYesUTC timestamp at which HelpMyAgent performed the check.
identifierYesIdentifier supplied for the request, echoed in normalized form when applicable.
identifier_typeYesNormalized identifier type, such as SIREN or SIRET when applicable. (allowed values: siren, siret).
sections_availableYesStructured value returned for “sections available” as defined by this API contract.
sections_requestedYesStructured value returned for “sections requested” as defined by this API contract.
sections_unavailableYesStructured value returned for “sections unavailable” as defined by this API contract.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / domain
      Added value: +{
+  "description": "Optional domain used by the compliance section; it is not treated as an officially verified company domain.",
+  "type": "string"
+}
  2. Changed14 schema fields changed
    • addedInput schema / description
      Added value: +"Structured input parameters for the company/fr/intelligence API."
    • addedOutput schema / description
      Added value: +"Structured result returned by the company/fr/intelligence API."
    • 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 / identifier_type / description
      Added value: +"Normalized identifier type, such as SIREN or SIRET when applicable. (allowed values: siren, siret)."
    • addedOutput schema / properties / name / description
      Added value: +"Publicly available company, person, buyer or record name for this result."
    • addedOutput schema / properties / sections / additionalProperties / properties / data / description
      Added value: +"Structured value returned for “data” as defined by this API contract."
    • addedOutput schema / properties / sections / additionalProperties / properties / status / description
      Added value: +"Normalized endpoint or source status. (allowed values: ok, unavailable, not_available)."
    • addedOutput schema / properties / sections / description
      Added value: +"Named result sections produced by this aggregator."
    • addedOutput schema / properties / sections_available / description
      Added value: +"Structured value returned for “sections available” as defined by this API contract."
    • addedOutput schema / properties / sections_requested / description
      Added value: +"Structured value returned for “sections requested” as defined by this API contract."
    • addedOutput schema / properties / sections_unavailable / description
      Added value: +"Structured value returned for “sections unavailable” as defined by this API contract."
    • addedOutput schema / properties / siren / description
      Added value: +"Normalized 9-digit French SIREN when available."
  3. First observed

TDQS

A4.4/5.0
Behavior4/5

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

The annotations only say readOnlyHint=false, openWorldHint=false, idempotentHint=false, destructiveHint=false, which is sparse. The description adds valuable behavioral context: it is an aggregator with no independent data source, it tolerates partial unavailability, and it consumes x402 payment. 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.

Conciseness4/5

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

The description is front-loaded with the defining aggregator statement, then uses clear headings for usage, limitations, and pricing. It is longer than strictly necessary due to detailed x402 payment behavior, but each section earns its place. The structure makes it easy for an agent 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?

For a composite tool with many optional sections, the description covers purpose, when to use, when not to use, alternatives, limitation, pricing, partial coverage behavior, and payment implications. With the output schema present and the parameter schema fully covering inputs, nothing critical is missing for an agent to correctly invoke this tool.

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 description coverage is 100%, covering all three parameters including the include enum and identifier pattern, so the description does not need to explain them. However it adds almost no semantic nuance: the list of sections in the description simply repeats the include enum, and it does not clarify the trade-offs between include selections or the optional domain behavior beyond what the schema already states.

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 verb ('Aggregates'), a clear resource ('existing French company intelligence services'), and its key property ('into a single call, with selectable sections'). It differentiates itself from the many sibling tools by positioning it as an aggregator versus dedicated endpoints and explicitly naming the legacy KYB bundle use case.

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 description provides explicit 'Use when' and 'Avoid when' guidance, naming the alternative approach ('call the dedicated endpoint directly') and the condition that makes the aggregator unsuitable ('You require every requested section to be available'). This gives an agent clear decision rules.

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