HelpMyAgent

French Company Certifications

company_fr_certifications

Aggregates and normalizes public certifications and qualifications available for a French company, including RGE, organic certification and Qualiopi. Use when: You need public RGE, organic/Bio or Qualiopi certifications and qualifications linked to a French company. You need one normalized response combining the supported public certification sources. Avoid when: You need an exhaustive registry of every possible certification, private label or ISO certification held by the company. You need to infer a certification that is not explicitly present in one of the supported public sources. Limitations: Coverage is limited to the RGE, Agence Bio and Qualiopi public datasets used by this endpoint. A temporarily unavailable source can make the result partial, and source validity/status fields remain authoritative. Price: 0.010 USD per call via x402.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`identifier`	Yes	9-digit SIREN or 14-digit SIRET

Output Schema

TableJSON Schema

Name	Required	Description	Default
`name`	Yes
`siren`	Yes
`exists`	Yes
`sources`	Yes
`identifier`	Yes
`certifications`	Yes
`identifier_type`	Yes
`certifications_count`	Yes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

First observedSep 6, 2026

TDQS

A4.5/5.0

Behavior4/5

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

The description goes beyond the annotations by disclosing coverage limitations, the possibility of partial results when a source is temporarily unavailable, and that source validity/status fields remain authoritative. This is useful behavioral context that complements the annotations rather than merely repeating them.

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 compact and well-structured with labeled sections for use, avoidance, limitations, and price. The main purpose is front-loaded, and every sentence provides actionable information without redundancy.

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?

Given the tool has one required parameter, an output schema, and relevant annotations, the description covers the remaining context: when to use it, what it supports, what its limitations are, and its cost. Nothing essential is missing for an agent to invoke it 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?

The input schema already provides 100% coverage for the single `identifier` parameter, including its pattern and description. The tool description does not add parameter-specific detail, but none is necessary given the schema's completeness, so a 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 resource: 'Aggregates and normalizes public certifications and qualifications available for a French company,' and names concrete examples (RGE, organic certification, Qualiopi). It also differentiates the tool from a broader registry through the 'Avoid when' clause, which clarifies exactly what it is not.

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?

The 'Use when' and 'Avoid when' sections give explicit conditions for selecting this tool versus alternatives, including 'You need one normalized response combining the supported public certification sources.' This leaves little room for an agent to misuse the tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All HelpMyAgent tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.3/5.0

Disambiguation3/5

Most endpoints target distinct resources, but several clusters are easy to confuse: company_fr_intelligence vs company_fr_kyb, company_fr_peers vs company_fr_competitors vs company_fr_public_contract_competitors, and company_fr_risk vs company_fr_default_score vs company_fr_payment_context. The descriptive names help, but the repetitive 'Use when' sections often restate the description rather than contrasting with nearby tools.

Naming Consistency4/5

The dominant convention is domain_fr_feature with consistent snake_case, e.g., company_fr_profile, company_fr_financials, company_fr_public_contracts, procurement_fr_search, which makes the family predictable. The three meta tools (describe_api, list_categories, search_apis) switch to a bare verb_noun style, and a few company_fr names use verbs while most use nouns, creating a minor inconsistency.

Tool Count2/5

With 30 tools, the surface exceeds the 25+ threshold and feels heavy for an agent to navigate, especially because aggregators like company_fr_intelligence and company_fr_kyb overlap with many single-purpose endpoints. The broad French-company data domain justifies a large number of endpoints, but several could be consolidated or split out to make the server more focused.

Completeness4/5

The set covers discovery, verification, profile, directors, financials, legal risk, compliance, public contracts, procurement, funding, benchmarking, signals, and aggregation, so core French-company workflows have no major dead ends. Minor gaps remain around beneficial-ownership/shareholder data and subscription-style monitoring, but those are explicitly outside the stated scope of most endpoints.

Resources

Need Help?