Skip to main content
Glama

HelpMyAgent

by io.github.helpmyagent
OverviewDiscussionsAdmin

Nearby French companies

company_fr_nearby

Searches French companies around geographic coordinates using the official public company search geolocation endpoint. Use when: Searches French companies around geographic coordinates using the official public company search geolocation endpoint. You have geographic coordinates and need French companies within a radius. You want optional NAF activity filtering around a physical location. Avoid when: You want structured B2B prospecting by region, size, legal form or certifications without coordinates; use company/fr/prospecting. You are searching for a known company by name or identifier; use company/fr/search. Limitations: Results depend on geocoded establishment data exposed by the public company-search source. A geographic match indicates proximity, not a commercial relationship or service area. Price: 0.010 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
limitNoMaximum number of records returned by this call. (minimum 1; maximum 25; default 10).
latitudeYesLatitude in decimal degrees for the centre of the geographic search. (minimum -90; maximum 90).
longitudeYesLongitude in decimal degrees for the centre of the geographic search. (minimum -180; maximum 180).
radius_kmNoSearch radius around the supplied coordinates, expressed in kilometres. (greater than 0; maximum 50; default 5).
activity_codeNoOptional French NAF activity code used to restrict nearby-company results.
activity_sectionNoOptional NAF activity section letter used to restrict nearby-company results.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
latitudeYesStructured value returned for “latitude” as defined by this API contract.
companiesYesStructured company records returned by the endpoint.
longitudeYesStructured value returned for “longitude” as defined by this API contract.
radius_kmYesStructured value returned for “radius km” as defined by this API contract.
truncatedYesWhether additional matching records existed beyond the returned result limit.
total_countYesTotal number of matching records reported by the source or endpoint.
activity_codeYesStructured value returned for “activity code” as defined by this API contract.
returned_countYesNumber of records included in this response.
activity_sectionYesStructured value returned for “activity section” as defined by this API contract.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed17 schema fields changed
    • addedInput schema / description
      Added value: +"Structured input parameters for the company/fr/nearby API."
    • addedInput schema / properties / activity_code / description
      Added value: +"Optional French NAF activity code used to restrict nearby-company results."
    • addedInput schema / properties / activity_section / description
      Added value: +"Optional NAF activity section letter used to restrict nearby-company results."
    • addedInput schema / properties / latitude / description
      Added value: +"Latitude in decimal degrees for the centre of the geographic search. (minimum -90; maximum 90)."
    • addedInput schema / properties / limit / description
      Added value: +"Maximum number of records returned by this call. (minimum 1; maximum 25; default 10)."
    • addedInput schema / properties / longitude / description
      Added value: +"Longitude in decimal degrees for the centre of the geographic search. (minimum -180; maximum 180)."
    • addedInput schema / properties / radius_km / description
      Added value: +"Search radius around the supplied coordinates, expressed in kilometres. (greater than 0; maximum 50; default 5)."
    • addedOutput schema / description
      Added value: +"Structured result returned by the company/fr/nearby API."
    • changedOutput schema / properties / activity_code
      Previous value: -[]New value: +{
+  "description": "Structured value returned for “activity code” as defined by this API contract."
+}
    • changedOutput schema / properties / activity_section
      Previous value: -[]New value: +{
+  "description": "Structured value returned for “activity section” as defined by this API contract."
+}
    • addedOutput schema / properties / companies / description
      Added value: +"Structured company records returned by the endpoint."
    • addedOutput schema / properties / latitude / description
      Added value: +"Structured value returned for “latitude” as defined by this API contract."
    • addedOutput schema / properties / longitude / description
      Added value: +"Structured value returned for “longitude” as defined by this API contract."
    • addedOutput schema / properties / radius_km / description
      Added value: +"Structured value returned for “radius km” 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.4/5.0
Behavior4/5

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

Annotations are all false and provide no safety profile, so the description carries the burden. It discloses that source records are not modified, that a paid invocation consumes x402 payment, that the payment challenge is free, that repeats may require new payment, and accepted networks. Minor gaps remain (e.g., no explicit mention of rate limits or error behavior) but the core side effects and data caveats are covered.

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?

Well-organized with labeled sections and no irrelevant content, but the first sentence is repeated verbatim as the opening of the Use when section, wasting a sentence. Otherwise concise and front-loaded.

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 tool with six parameters and an output schema, the description covers selection criteria, exclusions, limitations, pricing, payment side effects, and accepted networks. Nothing an agent needs to invoke it correctly is missing; return-value details are already provided by the output schema.

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%, so the schema already documents all six parameters. The description adds only general context (radius, NAF filtering) without new semantic details, which matches the baseline for high schema coverage.

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?

Description opens with a specific verb+resource: 'Searches French companies around geographic coordinates using the official public company search geolocation endpoint.' It clearly distinguishes from nearby siblings by naming company/fr/prospecting for coordinate-free B2B prospecting and company/fr/search for known-company lookups, so an agent can select correctly.

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?

Explicit Use when/Avoid when sections state concrete trigger conditions (having coordinates, wanting radius or NAF filtering) and name the alternatives (company/fr/prospecting, company/fr/search). Limitations also clarify when results should not be over-interpreted.

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