Skip to main content
Glama

HelpMyAgent

by io.github.helpmyagent
OverviewDiscussionsAdmin

French Company Signals

company_fr_signals

Detects explainable business signals from available French company data, including closure, insolvency, revenue changes, new filings, public contracts and certifications. Use when: You need explainable business signals derived from existing public Company data rather than raw records from one source. You want to detect supported signals such as closure, insolvency, revenue change, new financial filings, public contracts or certifications. Avoid when: You need the underlying raw financial, BODACC, contract or certification records; call the specialized endpoint instead. You need continuous monitoring or push alerts; this endpoint evaluates signals at request time and is not a subscription service. Limitations: Only the signal families explicitly implemented by the endpoint are evaluated; it is not a general predictive business-risk model. Coverage can be partial when one of the underlying public-data services is unavailable. 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
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.
signalsYesStructured value returned for “signals” as defined by this API contract.
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.
lookback_daysYesStructured value returned for “lookback days” as defined by this API contract.
signals_countYesStructured value returned for “signals count” as defined by this API contract.
identifier_typeYesNormalized identifier type, such as SIREN or SIRET when applicable. (allowed values: siren, siret).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed20 schema fields changed
    • addedInput schema / description
      Added value: +"Structured input parameters for the company/fr/signals API."
    • addedOutput schema / description
      Added value: +"Structured result returned by the company/fr/signals API."
    • addedOutput schema / properties / checked_at / description
      Added value: +"UTC timestamp at which HelpMyAgent performed the check."
    • addedOutput schema / properties / coverage / description
      Added value: +"Coverage information describing which underlying services or sources were available."
    • addedOutput schema / properties / coverage / items / properties / service / description
      Added value: +"Structured value returned for “service” as defined by this API contract."
    • addedOutput schema / properties / coverage / items / properties / status / description
      Added value: +"Normalized endpoint or source status."
    • 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 / lookback_days / description
      Added value: +"Structured value returned for “lookback days” as defined by this API contract."
    • addedOutput schema / properties / name / description
      Added value: +"Publicly available company, person, buyer or record name for this result."
    • addedOutput schema / properties / signals / description
      Added value: +"Structured value returned for “signals” as defined by this API contract."
    • addedOutput schema / properties / signals / items / properties / date / description
      Added value: +"Structured value returned for “date” as defined by this API contract."
    • addedOutput schema / properties / signals / items / properties / explanation / description
      Added value: +"Structured value returned for “explanation” as defined by this API contract."
    • addedOutput schema / properties / signals / items / properties / importance / description
      Added value: +"Structured value returned for “importance” as defined by this API contract. (allowed values: low, medium, high)."
    • addedOutput schema / properties / signals / items / properties / source_data / description
      Added value: +"Structured value returned for “source data” as defined by this API contract."
    • addedOutput schema / properties / signals / items / properties / sources / description
      Added value: +"Public data sources used or checked for this result."
    • addedOutput schema / properties / signals / items / properties / type / description
      Added value: +"Structured value returned for “type” as defined by this API contract. (allowed values: INSOLVENCY, REVENUE_DROP, FAST_GROWTH, NEW_FINANCIAL_STATEMENT, NEW_PUBLIC_CONTRACT, NEW_CERTIFICATION, COMPANY_CLOSED)."
    • addedOutput schema / properties / signals_count / description
      Added value: +"Structured value returned for “signals count” as defined by this API contract."
    • addedOutput schema / properties / siren / description
      Added value: +"Normalized 9-digit French SIREN when available."
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

With all annotations set to false, the description carries the full burden of behavioral disclosure. It clearly states that source records are not modified, that paid invocations may consume x402 payment, that the payment-required challenge is free, and that repeated calls may need new payment. It also discloses coverage limitations when underlying data services are unavailable. 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 well-structured with clear sections and front-loaded purpose. It is longer than minimal but every section adds relevant guidance; there is minor redundancy in repeating the signal list, but it is not distracting.

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?

Given the output schema exists, the description does not need to explain return values. It covers purpose, alternatives, limitations, pricing, payment side effects, and accepted networks, making it complete for an agent to decide when and how to 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?

The schema already documents the single 'identifier' parameter with its SIREN/SIRET pattern and description. The tool description adds no additional parameter-level semantics, so the baseline of 3 applies since the schema fully covers the parameter.

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 ('Detects') and resource ('explainable business signals from available French company data'), then enumerates the signal families. It clearly differentiates this tool from raw-record endpoints like financials or contracts, so an agent can tell what this endpoint is and is not.

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' sections, including concrete exclusions for raw financial, BODACC, contract, and certification records, plus the non-subscription caveat. This gives an agent direct routing guidance versus the many sibling tools.

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