Skip to main content
Glama

HelpMyAgent

by io.github.helpmyagent
OverviewDiscussionsAdmin

French Company Public Funding

company_fr_aids

Finds and ranks French public funding programs potentially relevant to a company based on its profile, location and project. Eligibility results are indicative and do not constitute an official eligibility decision. Use when: You need to find and rank French public funding schemes that may fit a company profile, territory and optional project. You need explainable matching reasons and known/unknown eligibility criteria before manually reviewing an aid program. Avoid when: You need an official eligibility decision, approval decision or automatic grant application. You need funding programs unrelated to the public Aides-entreprises dataset used by this endpoint. Limitations: potentially_eligible means only that automatically verifiable criteria show no known incompatibility; detailed conditions must still be checked. Some workforce, company-age, size-text and fine-grained geographic criteria can remain unknown, and very local schemes can be omitted when exact geographic matching is not possible. 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
limitNoMaximum number of ranked aid schemes to return
projectNoOptional project context used to rank matching public aid schemes
identifierYes9-digit SIREN or 14-digit SIRET

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
aidsYesRanked public funding schemes returned by the endpoint.
nameYesPublicly available company, person, buyer or record name for this result.
sirenYesNormalized 9-digit French SIREN when available.
existsYesWhether the requested company or public record was found in the checked source.
truncatedYesWhether additional matching records existed beyond the returned result limit.
identifierYesIdentifier supplied for the request, echoed in normalized form when applicable.
limitationsNoKnown interpretation, source-coverage or freshness limitations for this result.
company_statusYesCurrent public administrative company status when available.
returned_countYesNumber of records included in this response.
identifier_typeYesNormalized identifier type, such as SIREN or SIRET when applicable. (allowed values: siren, siret).
matching_contextYesStructured value returned for “matching context” as defined by this API contract.
total_candidatesYesStructured value returned for “total candidates” as defined by this API contract.
source_total_countYesStructured value returned for “source total 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: -[
-  "identifier",
-  "identifier_type",
-  "exists",
-  "siren",
-  "name",
-  "company_status",
-  "matching_context",
-  "source_total_count",
-  "total_candidates",
-  "returned_count",
-  "truncated",
-  "aids",
-  "limitations"
-]New value: +[
+  "identifier",
+  "identifier_type",
+  "exists",
+  "siren",
+  "name",
+  "company_status",
+  "matching_context",
+  "source_total_count",
+  "total_candidates",
+  "returned_count",
+  "truncated",
+  "aids"
+]
  2. Changed42 schema fields changed
    • addedInput schema / description
      Added value: +"Structured input parameters for the company/fr/aids API."
    • addedOutput schema / description
      Added value: +"Structured result returned by the company/fr/aids API."
    • addedOutput schema / properties / aids / description
      Added value: +"Ranked public funding schemes returned by the endpoint."
    • addedOutput schema / properties / aids / items / properties / amount / description
      Added value: +"Structured value returned for “amount” as defined by this API contract."
    • addedOutput schema / properties / aids / items / properties / application_links / description
      Added value: +"Structured value returned for “application links” as defined by this API contract."
    • addedOutput schema / properties / aids / items / properties / beneficiaries / description
      Added value: +"Structured value returned for “beneficiaries” as defined by this API contract."
    • addedOutput schema / properties / aids / items / properties / conditions / description
      Added value: +"Structured value returned for “conditions” as defined by this API contract."
    • addedOutput schema / properties / aids / items / properties / contacts / description
      Added value: +"Structured value returned for “contacts” as defined by this API contract."
    • addedOutput schema / properties / aids / items / properties / id / description
      Added value: +"Structured value returned for “id” as defined by this API contract."
    • addedOutput schema / properties / aids / items / properties / match / description
      Added value: +"Structured value returned for “match” as defined by this API contract."
    • addedOutput schema / properties / aids / items / properties / match / properties / matched_profile / description
      Added value: +"Structured value returned for “matched profile” as defined by this API contract."
    • addedOutput schema / properties / aids / items / properties / match / properties / matched_project / description
      Added value: +"Structured value returned for “matched project” as defined by this API contract."
    • addedOutput schema / properties / aids / items / properties / match / properties / matched_territory / description
      Added value: +"Structured value returned for “matched territory” as defined by this API contract."
    • addedOutput schema / properties / aids / items / properties / match / properties / potentially_eligible / description
      Added value: +"Structured value returned for “potentially eligible” as defined by this API contract."
    • addedOutput schema / properties / aids / items / properties / match / properties / reasons / description
      Added value: +"Structured value returned for “reasons” as defined by this API contract."
    • addedOutput schema / properties / aids / items / properties / match / properties / score / description
      Added value: +"Normalized score produced by the endpoint; interpretation is defined by the tool description and limitations."
    • addedOutput schema / properties / aids / items / properties / match / properties / unknown_criteria / description
      Added value: +"Structured value returned for “unknown criteria” as defined by this API contract."
    • addedOutput schema / properties / aids / items / properties / match / properties / verified_criteria / description
      Added value: +"Structured value returned for “verified criteria” as defined by this API contract."
    • addedOutput schema / properties / aids / items / properties / name / description
      Added value: +"Publicly available company, person, buyer or record name for this result."
    • addedOutput schema / properties / aids / items / properties / natures / description
      Added value: +"Structured value returned for “natures” as defined by this API contract."
    • addedOutput schema / properties / aids / items / properties / object / description
      Added value: +"Structured value returned for “object” as defined by this API contract."
    • addedOutput schema / properties / aids / items / properties / operations / description
      Added value: +"Structured value returned for “operations” as defined by this API contract."
    • addedOutput schema / properties / aids / items / properties / profiles / description
      Added value: +"Structured value returned for “profiles” as defined by this API contract."
    • addedOutput schema / properties / aids / items / properties / projects / description
      Added value: +"Structured value returned for “projects” as defined by this API contract."
    • addedOutput schema / properties / aids / items / properties / source / description
      Added value: +"Structured value returned for “source” as defined by this API contract."
    • addedOutput schema / properties / aids / items / properties / source_links / description
      Added value: +"Structured value returned for “source links” as defined by this API contract."
    • addedOutput schema / properties / aids / items / properties / source_type / description
      Added value: +"Structured value returned for “source type” as defined by this API contract. (allowed values: SOURCE_PUBLIQUE)."
    • addedOutput schema / properties / aids / items / properties / territories / description
      Added value: +"Structured value returned for “territories” as defined by this API contract."
    • addedOutput schema / properties / aids / items / properties / valid_until / description
      Added value: +"Structured value returned for “valid until” as defined by this API contract."
    • addedOutput schema / properties / aids / items / properties / validation_date / description
      Added value: +"Structured value returned for “validation date” as defined by this API contract."
    • addedOutput schema / properties / company_status / description
      Added value: +"Current public administrative company status when available."
    • addedOutput schema / properties / exists / description
      Added value: +"Whether the requested company or public record was found in the checked source."
    • addedOutput schema / properties / identifier / description
      Added value: +"Identifier supplied for the request, echoed in normalized form when applicable."
    • addedOutput schema / properties / identifier_type / description
      Added value: +"Normalized identifier type, such as SIREN or SIRET when applicable. (allowed values: siren, siret)."
    • addedOutput schema / properties / limitations / description
      Added value: +"Known interpretation, source-coverage or freshness limitations for this result."
    • addedOutput schema / properties / matching_context / description
      Added value: +"Structured value returned for “matching context” as defined by this API contract."
    • addedOutput schema / properties / name / description
      Added value: +"Publicly available company, person, buyer or record name for this result."
    • addedOutput schema / properties / returned_count / description
      Added value: +"Number of records included in this response."
    • addedOutput schema / properties / siren / description
      Added value: +"Normalized 9-digit French SIREN when available."
    • addedOutput schema / properties / source_total_count / description
      Added value: +"Structured value returned for “source total count” as defined by this API contract."
    • addedOutput schema / properties / total_candidates / description
      Added value: +"Structured value returned for “total candidates” as defined by this API contract."
    • addedOutput schema / properties / truncated / description
      Added value: +"Whether additional matching records existed beyond the returned result limit."
  3. First observed

TDQS

A4.5/5.0
Behavior5/5

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

The description transparently discloses that results are indicative, that 'potentially_eligible' only means no known incompatibility, and that the call consumes an x402 payment. It also clarifies that source records are not modified, which is important given the annotations do not flag the call as read-only or idempotent.

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

Conciseness5/5

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

The description is well-structured with clear sections: purpose, usage guidance, limitations, pricing, and payment behavior. It is front-loaded with the core action and every section adds necessary operational information for a paid API endpoint.

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 paid-call behavior, nuanced eligibility semantics, and a limited parameter set, the description covers all needed context: what it does, when to use it, when to avoid it, limitations, cost, and payment behavior. Output schema presence means return-value details do not need to be described.

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 documents all three parameters with descriptions and 100% coverage, so the baseline is 3. The description adds contextual meaning by mentioning profile, location, and project, but it does not add parameter syntax or format details 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 opens with a specific verb and resource: 'Finds and ranks French public funding programs potentially relevant to a company.' It also differentiates from siblings by scoping to the Aides-entreprises dataset and by explicitly excluding official eligibility decisions and automatic grant applications.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit 'Use when' and 'Avoid when' sections, including conditions such as needing explainable matching reasons and avoiding official eligibility decisions. It does not name a specific alternative tool, so it stops short of a 5, but the context is clear and actionable.

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