Skip to main content
Glama

HelpMyAgent

by io.github.helpmyagent
OverviewDiscussionsAdmin

French B2B company prospecting

company_fr_prospecting

Searches active French companies using structured public B2B filters such as activity, geography, size and supported certifications. Use when: Searches active French companies using structured public B2B filters such as activity, geography, size and supported certifications. You need a list of active French companies matching structured B2B criteria such as activity, geography, size or supported certifications. You want prospect candidates before running deeper company checks. Avoid when: You are looking for one known company by name, SIREN or SIRET; use company/fr/search. You need a radius search around coordinates; use company/fr/nearby. Limitations: Prospecting coverage follows the public company and certification sources used by the selected filters. A filter match is a discovery signal, not proof of commercial suitability or current willingness to buy. 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
bioNoWhen true, restrict results to companies found in the supported public organic/Bio certification source.
rgeNoWhen true, restrict results to companies with a supported public RGE qualification.
pageNoOne-based result page number. (minimum 1; default 1).
limitNoMaximum number of records returned by this call. (minimum 1; maximum 25; default 25).
queryNoOptional company-name or free-text term combined with the structured prospecting filters.
regionNoOptional French region code used to restrict results geographically.
qualiopiNoWhen true, restrict results to companies found in the supported public Qualiopi source.
departmentNoOptional French department code used to restrict results geographically.
postal_codeNoOptional French postal code used to narrow results geographically.
activity_codeNoOptional French NAF activity code used to restrict or classify company results.
legal_form_codeNoOptional French legal-form code used to restrict company results.
activity_sectionNoOptional NAF activity section used to restrict company results.
company_categoryNoOptional French company-size category used to restrict prospecting results.
employee_band_codeNoOptional official employee-band code used to restrict company results.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageYesStructured value returned for “page” as defined by this API contract.
limitYesStructured value returned for “limit” as defined by this API contract.
filtersYesStructured value returned for “filters” as defined by this API contract.
companiesYesStructured company records returned by the endpoint.
truncatedYesWhether additional matching records existed beyond the returned result limit.
total_countYesTotal number of matching records reported by the source or endpoint.
returned_countYesNumber of records included in this response.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed23 schema fields changed
    • addedInput schema / description
      Added value: +"Structured input parameters for the company/fr/prospecting API."
    • addedInput schema / properties / activity_code / description
      Added value: +"Optional French NAF activity code used to restrict or classify company results."
    • addedInput schema / properties / activity_section / description
      Added value: +"Optional NAF activity section used to restrict company results."
    • addedInput schema / properties / bio / description
      Added value: +"When true, restrict results to companies found in the supported public organic/Bio certification source."
    • addedInput schema / properties / company_category / description
      Added value: +"Optional French company-size category used to restrict prospecting results."
    • addedInput schema / properties / department / description
      Added value: +"Optional French department code used to restrict results geographically."
    • addedInput schema / properties / employee_band_code / description
      Added value: +"Optional official employee-band code used to restrict company results."
    • addedInput schema / properties / legal_form_code / description
      Added value: +"Optional French legal-form code used to restrict company results."
    • addedInput schema / properties / limit / description
      Added value: +"Maximum number of records returned by this call. (minimum 1; maximum 25; default 25)."
    • addedInput schema / properties / page / description
      Added value: +"One-based result page number. (minimum 1; default 1)."
    • addedInput schema / properties / postal_code / description
      Added value: +"Optional French postal code used to narrow results geographically."
    • addedInput schema / properties / qualiopi / description
      Added value: +"When true, restrict results to companies found in the supported public Qualiopi source."
    • addedInput schema / properties / query / description
      Added value: +"Optional company-name or free-text term combined with the structured prospecting filters."
    • addedInput schema / properties / region / description
      Added value: +"Optional French region code used to restrict results geographically."
    • addedInput schema / properties / rge / description
      Added value: +"When true, restrict results to companies with a supported public RGE qualification."
    • addedOutput schema / description
      Added value: +"Structured result returned by the company/fr/prospecting API."
    • addedOutput schema / properties / companies / description
      Added value: +"Structured company records returned by the endpoint."
    • addedOutput schema / properties / filters / description
      Added value: +"Structured value returned for “filters” as defined by this API contract."
    • addedOutput schema / properties / limit / description
      Added value: +"Structured value returned for “limit” as defined by this API contract."
    • addedOutput schema / properties / page / description
      Added value: +"Structured value returned for “page” as defined by this API contract."
    • addedOutput schema / properties / returned_count / description
      Added value: +"Number of records included in this response."
    • addedOutput schema / properties / total_count / description
      Added value: +"Total number of matching records reported by the source or endpoint."
    • addedOutput schema / properties / truncated / description
      Added value: +"Whether additional matching records existed beyond the returned result limit."
  2. Added

TDQS

A4.5/5.0
Behavior5/5

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

Annotations only indicate not read-only, not idempotent, and not destructive; the description adds critical behavioral context: source records are not modified, paid invocations can consume x402 payment, the payment challenge is free, and repeating a paid call may require a new payment. It also notes coverage limitations and that matches are discovery signals, which is valuable beyond annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The description is front-loaded and contains useful sections, but the first sentence is repeated almost verbatim in the 'Use when' section. This redundancy costs conciseness even though the overall structure is clear.

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 14-parameter optional-filter tool with an output schema, the description covers use cases, avoid cases, alternatives, limitations, pricing, payment behavior, and accepted networks. Nothing critical appears missing for an agent to decide whether 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 input schema already covers 100% of parameters with individual descriptions, so the description does not need to repeat them. It adds general filter categories (activity, geography, size, certifications) but no parameter-specific semantics beyond the schema, 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 states a specific action and resource: 'Searches active French companies using structured public B2B filters such as activity, geography, size and supported certifications.' It also names alternatives for related lookups (search, nearby), so an agent can distinguish it from siblings without opening the schema.

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?

Provides explicit 'Use when' and 'Avoid when' sections with concrete sibling alternatives: company/fr/search for single known companies and company/fr/nearby for radius searches. This gives clear routing guidance beyond the unstructured schema.

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