Skip to main content
Glama

HelpMyAgent

by io.github.helpmyagent
OverviewDiscussionsAdmin

French Company PDF Report

company_fr_report

Generates a simple PDF rendition of selected HelpMyAgent public company intelligence. Use when: Generate a portable PDF summary for a French company. You need a portable PDF summary of selected HelpMyAgent public company intelligence. You need a human-readable artifact in French or English rather than only structured JSON. Avoid when: You need structured data for downstream automation; use company/fr/intelligence or a dedicated endpoint. You only need a written risk interpretation; use company/fr/risk-reading. Limitations: The PDF reflects the public-data sections available when it is generated and does not add independent factual coverage. It is an informational report, not an audit, legal opinion or regulated credit report. Price: 0.075 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
bytesYesStructured value returned for “bytes” as defined by this API contract.
sha256YesStructured value returned for “sha256” as defined by this API contract.
filenameYesStructured value returned for “filename” as defined by this API contract.
languageYesStructured value returned for “language” as defined by this API contract.
sectionsYesNamed result sections produced by this aggregator.
mime_typeYesStructured value returned for “mime type” as defined by this API contract.
identifierYesIdentifier supplied for the request, echoed in normalized form when applicable.
pdf_base64YesStructured value returned for “pdf base64” as defined by this API contract.
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",
-  "language",
-  "filename",
-  "mime_type",
-  "bytes",
-  "sha256",
-  "pdf_base64",
-  "sections",
-  "generated_at",
-  "limitations"
-]New value: +[
+  "identifier",
+  "language",
+  "filename",
+  "mime_type",
+  "bytes",
+  "sha256",
+  "pdf_base64",
+  "sections",
+  "generated_at"
+]
  2. Changed14 schema fields changed
    • addedInput schema / description
      Added value: +"Structured input parameters for the company/fr/report 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/report API."
    • addedOutput schema / properties / bytes / description
      Added value: +"Structured value returned for “bytes” as defined by this API contract."
    • addedOutput schema / properties / filename / description
      Added value: +"Structured value returned for “filename” as defined by this API contract."
    • 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 / mime_type / description
      Added value: +"Structured value returned for “mime type” as defined by this API contract."
    • addedOutput schema / properties / pdf_base64 / description
      Added value: +"Structured value returned for “pdf base64” as defined by this API contract."
    • addedOutput schema / properties / sections / description
      Added value: +"Named result sections produced by this aggregator."
    • addedOutput schema / properties / sha256 / description
      Added value: +"Structured value returned for “sha256” as defined by this API contract."
  3. Added

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the sparse annotations, the description thoroughly discloses behavior: paid-call consumption via x402, free payment challenge, no source-record modification, and the informational limitations (not audit, legal opinion, or regulated credit report). This is valuable context the annotations do not provide.

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-organized with clear sections: use, avoid, limitations, price, and paid-call behavior. It is slightly longer than strictly necessary and shows minor redundancy between the opening sentence and the 'Use when' line, but every section 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?

For a two-parameter tool with a full input schema, output schema, explicit usage routing, pricing, payment side effects, and limitations, the description leaves nothing material for an agent to infer. It is complete for correct selection and invocation.

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 coverage is 100%, and the input schema already fully documents the identifier pattern and language enum. The description reinforces French/English output and portability, but adds no meaningful parameter semantics beyond what the schema provides, so baseline 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 artifact: 'Generates a simple PDF rendition of selected HelpMyAgent public company intelligence.' It clearly distinguishes this tool from structured-data siblings and the risk-reading tool through explicit avoid conditions.

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, naming alternatives such as company/fr/intelligence for structured data and company/fr/risk-reading for risk interpretation. An agent can correctly route between this tool and its siblings without guessing.

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