Skip to main content
Glama

HelpMyAgent

by io.github.helpmyagent
OverviewDiscussionsAdmin

French Company Profile

company_fr_profile

Returns the public profile of a French company from a SIREN or SIRET. Use when: You need a normalized public administrative profile for a French company from its SIREN or SIRET. You need headquarters, activity, legal-form, creation-date, employee-band or establishment-count fields in one response. Avoid when: You only need a yes/no existence or active-status check; use company/fr/verify. You need directors, financial statements, legal risk or compliance results; use the dedicated endpoint. Limitations: Some profile fields can be null when the public source does not expose them for the company. This endpoint does not replace the specialized directors, financials, risk or compliance endpoints. Price: 0.005 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
identifierYes9-digit SIREN or 14-digit SIRET

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
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.
statusYesNormalized endpoint or source status.
identifierYesIdentifier supplied for the request, echoed in normalized form when applicable.
is_employerYesStructured value returned for “is employer” as defined by this API contract.
closure_dateYesStructured value returned for “closure date” as defined by this API contract.
headquartersYesStructured value returned for “headquarters” as defined by this API contract.
activity_codeYesStructured value returned for “activity code” as defined by this API contract.
creation_dateYesStructured value returned for “creation date” as defined by this API contract.
identifier_typeYesNormalized identifier type, such as SIREN or SIRET when applicable. (allowed values: siren, siret).
legal_form_codeYesStructured value returned for “legal form code” as defined by this API contract.
company_categoryYesStructured value returned for “company category” as defined by this API contract.
employee_band_codeYesStructured value returned for “employee band code” as defined by this API contract.
employee_band_yearYesStructured value returned for “employee band year” as defined by this API contract.
establishments_countYesStructured value returned for “establishments count” as defined by this API contract.
open_establishments_countYesStructured value returned for “open establishments count” as defined by this API contract.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed30 schema fields changed
    • addedInput schema / description
      Added value: +"Structured input parameters for the company/fr/profile API."
    • addedOutput schema / description
      Added value: +"Structured result returned by the company/fr/profile API."
    • addedOutput schema / properties / activity_code / description
      Added value: +"Structured value returned for “activity code” as defined by this API contract."
    • addedOutput schema / properties / closure_date / description
      Added value: +"Structured value returned for “closure date” as defined by this API contract."
    • addedOutput schema / properties / company_category / description
      Added value: +"Structured value returned for “company category” as defined by this API contract."
    • addedOutput schema / properties / creation_date / description
      Added value: +"Structured value returned for “creation date” as defined by this API contract."
    • addedOutput schema / properties / employee_band_code / description
      Added value: +"Structured value returned for “employee band code” as defined by this API contract."
    • addedOutput schema / properties / employee_band_year / description
      Added value: +"Structured value returned for “employee band year” as defined by this API contract."
    • addedOutput schema / properties / establishments_count / description
      Added value: +"Structured value returned for “establishments count” as defined by this API contract."
    • addedOutput schema / properties / exists / description
      Added value: +"Whether the requested company or public record was found in the checked source."
    • addedOutput schema / properties / headquarters / description
      Added value: +"Structured value returned for “headquarters” as defined by this API contract."
    • addedOutput schema / properties / headquarters / properties / activity_code / description
      Added value: +"Structured value returned for “activity code” as defined by this API contract."
    • addedOutput schema / properties / headquarters / properties / address / description
      Added value: +"Structured value returned for “address” as defined by this API contract."
    • addedOutput schema / properties / headquarters / properties / city / description
      Added value: +"Structured value returned for “city” as defined by this API contract."
    • addedOutput schema / properties / headquarters / properties / creation_date / description
      Added value: +"Structured value returned for “creation date” as defined by this API contract."
    • addedOutput schema / properties / headquarters / properties / department / description
      Added value: +"Structured value returned for “department” as defined by this API contract."
    • addedOutput schema / properties / headquarters / properties / latitude / description
      Added value: +"Structured value returned for “latitude” as defined by this API contract."
    • addedOutput schema / properties / headquarters / properties / longitude / description
      Added value: +"Structured value returned for “longitude” as defined by this API contract."
    • addedOutput schema / properties / headquarters / properties / postal_code / description
      Added value: +"Structured value returned for “postal code” as defined by this API contract."
    • addedOutput schema / properties / headquarters / properties / region / description
      Added value: +"Structured value returned for “region” as defined by this API contract."
    • addedOutput schema / properties / headquarters / properties / siret / description
      Added value: +"Normalized 14-digit French SIRET when available."
    • addedOutput schema / properties / headquarters / properties / status / description
      Added value: +"Normalized endpoint or source status."
    • 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 / is_employer / description
      Added value: +"Structured value returned for “is employer” as defined by this API contract."
    • addedOutput schema / properties / legal_form_code / description
      Added value: +"Structured value returned for “legal form code” 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 / open_establishments_count / description
      Added value: +"Structured value returned for “open establishments count” as defined by this API contract."
    • addedOutput schema / properties / siren / description
      Added value: +"Normalized 9-digit French SIREN when available."
    • addedOutput schema / properties / status / description
      Added value: +"Normalized endpoint or source status."
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

The description openly discloses limitations (nullable fields), paid-call behavior (payment consumed, free challenge, new payment on repeat), and the fact that source records are not modified. With all annotations set to false or unhelpful, this description carries the full behavioral burden and does so thoroughly.

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: core behavior, use/avoid guidance, limitations, pricing, and side-effect behavior. Each section earns its place, and the most important information is front-loaded. Despite covering many aspects, it remains scannable and purposeful.

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 single-parameter tool with an output schema and a crowded sibling set, the description is complete: it states what the tool returns, when to use it, when not to use it, what its limitations are, and what side effects to expect. Nothing essential for correct selection or invocation is missing.

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 coverage is 100%, so the description gains little extra credit for parameters. The identifier parameter is fully documented in the schema with its pattern, and the description simply reiterates that a SIREN or SIRET is accepted. This meets the baseline but adds no new semantic detail.

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 clear verb and resource: 'Returns the public profile of a French company from a SIREN or SIRET.' It also distinguishes itself from sibling tools by naming the verify endpoint for existence checks and the dedicated endpoints for directors, financials, and risk. This makes the tool's purpose unambiguous.

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 provide explicit decision criteria and name specific alternatives, such as company/fr/verify and the specialized directors/financials/risk endpoints. This is exactly the kind of routing guidance an agent needs to select correctly among many 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