Skip to main content
Glama

HelpMyAgent

by io.github.helpmyagent
OverviewDiscussionsAdmin

French Company Risk Reading

company_fr_risk_reading

Turns existing public risk, legal, financial and signal data into a concise written reading. Use when: Get a written public-data risk reading for a French company. You need a concise human-readable interpretation of existing public risk, legal, financial and signal data. You want strengths, alerts and evidence summarized in French or English. Avoid when: You need structured legal-risk events and level only; use company/fr/risk. You need the deterministic public-data default indicator and components; use company/fr/default-score. Limitations: The narrative is derived from existing HelpMyAgent public-data results and does not create new source evidence. It is informational and must not be treated as a regulated credit or legal decision. Price: 0.030 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
languageNoLanguage used for the generated human-readable output. (default fr; allowed values: fr, en).fr
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.
scoreYesNormalized score produced by the endpoint; interpretation is defined by the tool description and limitations.
sirenYesNormalized 9-digit French SIREN when available.
alertsYesStructured value returned for “alerts” as defined by this API contract.
existsYesWhether the requested company or public record was found in the checked source.
verdictYesNormalized endpoint conclusion derived from the checked public data.
evidenceYesStructured value returned for “evidence” as defined by this API contract.
languageYesStructured value returned for “language” as defined by this API contract.
narrativeYesStructured value returned for “narrative” as defined by this API contract.
strengthsYesStructured value returned for “strengths” as defined by this API contract.
confidenceYesConfidence indicator associated with an inferred or derived result.
identifierYesIdentifier supplied for the request, echoed in normalized form when applicable.
limitationsNoKnown interpretation, source-coverage or freshness limitations for this result.
generated_atYesUTC timestamp at which this derived result was generated.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / required
      Previous value: -[
-  "identifier",
-  "exists",
-  "siren",
-  "name",
-  "language",
-  "verdict",
-  "score",
-  "confidence",
-  "narrative",
-  "strengths",
-  "alerts",
-  "evidence",
-  "generated_at",
-  "limitations"
-]New value: +[
+  "identifier",
+  "exists",
+  "siren",
+  "name",
+  "language",
+  "verdict",
+  "score",
+  "confidence",
+  "narrative",
+  "strengths",
+  "alerts",
+  "evidence",
+  "generated_at"
+]
  2. Changed18 schema fields changed
    • addedInput schema / description
      Added value: +"Structured input parameters for the company/fr/risk-reading API."
    • addedInput schema / properties / identifier / description
      Added value: +"French company identifier: 9-digit SIREN or 14-digit SIRET."
    • addedInput schema / properties / language / description
      Added value: +"Language used for the generated human-readable output. (default fr; allowed values: fr, en)."
    • addedOutput schema / description
      Added value: +"Structured result returned by the company/fr/risk-reading API."
    • addedOutput schema / properties / alerts / description
      Added value: +"Structured value returned for “alerts” as defined by this API contract."
    • addedOutput schema / properties / confidence / description
      Added value: +"Confidence indicator associated with an inferred or derived result."
    • addedOutput schema / properties / evidence / description
      Added value: +"Structured value returned for “evidence” 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 / generated_at / description
      Added value: +"UTC timestamp at which this derived result was generated."
    • addedOutput schema / properties / identifier / description
      Added value: +"Identifier supplied for the request, echoed in normalized form when applicable."
    • addedOutput schema / properties / language / description
      Added value: +"Structured value returned for “language” as defined by this API contract."
    • 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 / narrative / description
      Added value: +"Structured value returned for “narrative” as defined by this API contract."
    • addedOutput schema / properties / score / description
      Added value: +"Normalized score produced by the endpoint; interpretation is defined by the tool description and limitations."
    • addedOutput schema / properties / siren / description
      Added value: +"Normalized 9-digit French SIREN when available."
    • addedOutput schema / properties / strengths / description
      Added value: +"Structured value returned for “strengths” as defined by this API contract."
    • addedOutput schema / properties / verdict / description
      Added value: +"Normalized endpoint conclusion derived from the checked public data."
  3. Added

TDQS

A4.6/5.0
Behavior5/5

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

The description goes well beyond the sparse annotations: it discloses that the narrative is derived from existing public-data results and creates no new evidence, that it is informational and not a regulated credit/legal decision, and that paid x402 calls do not modify source records but may consume payment and require new payment on repetition. This is strong behavioral disclosure.

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 longer than average, but it is clearly structured into use-when, avoid-when, limitations, price, paid-call behavior, and accepted networks. Every block adds decision-relevant information, though some phrasing could be tightened.

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 two-parameter paid tool, the description covers purpose, usage boundaries, limitations, pricing, payment behavior, accepted networks, and output language options. With an output schema present, no essential selection or invocation context 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?

The schema already provides complete descriptions for both parameters, including the SIREN/SIRET pattern and the language enum/default. The description adds only generic context about French companies and language, so it does not meaningfully increase parameter understanding beyond the schema.

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 names a specific verb and resource: it 'Turns existing public risk, legal, financial and signal data into a concise written reading' for a French company. It also distinguishes itself from siblings by explicitly pointing to company/fr/risk and company/fr/default-score for structured alternatives.

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?

It provides explicit 'Use when' and 'Avoid when' guidance, including the specific sibling tools to use instead when structured risk events or default indicators are needed. This leaves no ambiguity about when this tool is appropriate.

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