Skip to main content
Glama

HelpMyAgent

by io.github.helpmyagent
OverviewDiscussionsAdmin

French Company KYB Batch

company_fr_kyb_batch

Runs the existing public-data KYB dossier for 2 to 10 French company identifiers. Use when: Screen a batch of French suppliers with the public-data KYB dossier. You need the existing public-data KYB dossier for several French company identifiers in one call. You are screening a small supplier batch and need per-company success/failure results. Avoid when: You have only one company; use company/fr/intelligence with the KYB sections profile, directors, financials, risk and compliance. You specifically need VAT or IBAN consistency checks during supplier onboarding; use company/fr/supplier-verification. Limitations: Each item inherits the source coverage of the corresponding company/fr/intelligence sections. One company can fail or be partial without implying the same status for the other batch items. Price: 0.100 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
identifiersYesList of French company identifiers to process; each item must be a 9-digit SIREN or 14-digit SIRET. (at least 2 items; at most 10 items).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultsYesStructured result records returned by the endpoint.
checked_atYesUTC timestamp at which HelpMyAgent performed the check.
limitationsNoKnown interpretation, source-coverage or freshness limitations for this result.
failed_countYesStructured value returned for “failed count” as defined by this API contract.
completed_countYesStructured value returned for “completed count” as defined by this API contract.
requested_countYesStructured value returned for “requested count” as defined by this API contract.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / required
      Previous value: -[
-  "requested_count",
-  "completed_count",
-  "failed_count",
-  "results",
-  "checked_at",
-  "limitations"
-]New value: +[
+  "requested_count",
+  "completed_count",
+  "failed_count",
+  "results",
+  "checked_at"
+]
  2. Changed13 schema fields changed
    • addedInput schema / description
      Added value: +"Structured input parameters for the company/fr/kyb-batch API."
    • addedInput schema / properties / identifiers / description
      Added value: +"List of French company identifiers to process; each item must be a 9-digit SIREN or 14-digit SIRET. (at least 2 items; at most 10 items)."
    • addedOutput schema / description
      Added value: +"Structured result returned by the company/fr/kyb-batch API."
    • addedOutput schema / properties / checked_at / description
      Added value: +"UTC timestamp at which HelpMyAgent performed the check."
    • addedOutput schema / properties / completed_count / description
      Added value: +"Structured value returned for “completed count” as defined by this API contract."
    • addedOutput schema / properties / failed_count / description
      Added value: +"Structured value returned for “failed count” 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 / requested_count / description
      Added value: +"Structured value returned for “requested count” as defined by this API contract."
    • addedOutput schema / properties / results / description
      Added value: +"Structured result records returned by the endpoint."
    • addedOutput schema / properties / results / items / properties / data / description
      Added value: +"Structured value returned for “data” as defined by this API contract."
    • addedOutput schema / properties / results / items / properties / error / description
      Added value: +"Structured value returned for “error” as defined by this API contract."
    • addedOutput schema / properties / results / items / properties / identifier / description
      Added value: +"Identifier supplied for the request, echoed in normalized form when applicable."
    • addedOutput schema / properties / results / items / properties / status / description
      Added value: +"Normalized endpoint or source status."
  3. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only carry readOnlyHint=false, openWorldHint=false, idempotentHint=false, destructiveHint=false. Description adds critical non-obvious behavior: source records are not modified, paid calls consume x402 payment, payment-required challenge is free, repeat calls may require new payment, and batch items are independent. These go beyond structured 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?

Description is clearly structured with labeled sections (Use when, Avoid when, Limitations, Price) and front-loaded purpose. Slight redundancy in 'Use when' — three overlapping statements about needing multiple identifiers and batch screening — could be condensed, but overall 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?

Despite having only one parameter and an output schema, the description covers purpose, usage triggers, exclusions, limitations, per-item behavior, pricing, paid-call semantics, and accepted x402 networks. This is complete for an agent to decide and invoke the tool correctly.

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% and fully documents the 'identifiers' parameter (SIREN/SIRET formats, min/max, uniqueness). The tool description adds no new parameter semantics beyond restating 'French company identifiers', 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 first sentence states a specific verb ('Runs'), a resource ('public-data KYB dossier'), and a scope ('2 to 10 French company identifiers'). The Avoid-when clause explicitly names sibling tools and the condition that selects them (single company -> company/fr/intelligence; VAT/IBAN checks -> supplier-verification), making differentiation clear.

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?

Description provides explicit 'Use when' with specific scenarios (small supplier batch, need per-company results) and 'Avoid when' with alternatives and conditions (single company, VAT/IBAN checks). This directly answers when to use the tool versus siblings.

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