Skip to main content
Glama

Search French companies by name or SIREN/SIRET

company_fr
Read-only

Searches French companies via the official open API (recherche-entreprises.api.gouv.fr, Licence Ouverte v2). Returns legal name, SIREN, head-office SIRET and address, legal form, NAF activity code (no label in the API), creation date, status, size band, and directors when published. Rate limit: ~10 req/s (API's own limit). limit max 25. Related tools on this server, for a different need: company_br when you need to return Brazilian company data from BrasilAPI: legal name; company_registry when you need to search companies in Norway, Finland, Czechia and Poland. Price: $0.003 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "q": "<q>"
    },
    "name": "company_fr"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesCompany name, SIREN (9 digits) or SIRET (14 digits) to search
limitNoMax results (1–25, default 10)

Output Schema

NameRequiredDescriptionDefault
countNo
totalNo
sourceNo
resultsNo
checkedAtNo
disclaimerNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Beyond the readOnly/openWorld annotations, the description discloses the rate limit (~10 req/s, the API's own), the effective `limit` ceiling of 25, the paid-call model with x402 and the fact that failed calls are not charged. That is substantial operational context. It stops short of saying what happens on ambiguous or zero-match queries and gives no pagination behavior, which keeps it off a 5.

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?

Front-loaded with the verb, resource and scope, then source, return fields, limits, sibling routing and pricing in a single dense paragraph. Nearly every clause earns its place, though the pricing/network enumeration ("USDC on Base, Solana and 10 more networks") is boilerplate that could be trimmed without losing decision-relevant information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so the enumerated return fields are partly redundant, but the description still adds what the schema cannot: source and license, rate limit, cost model, and a hard cap on results. Nothing an agent needs to call this correctly appears to be missing; only edge-case behavior (no matches, ambiguous identifiers) is unaddressed.

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 both `q` and `limit` are already documented, and the description's "`limit` max 25" largely restates the schema's "1–25, default 10". The note that NAF codes come back without a label is useful but concerns output, not input semantics. Baseline 3 applies.

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?

States a specific verb and resource ("Searches French companies") plus the identifier types accepted (name, SIREN, SIRET) and the upstream source, and explicitly names the sibling tools it is not (company_br for Brazil, company_registry for Norway/Finland/Czechia/Poland). An agent can separate it from siblings without opening any 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?

The "Related tools on this server, for a different need" clause routes the agent explicitly: use company_br for Brazilian data, company_registry for Nordic/Central European data, implying this one is the French path. Alternatives and their selecting conditions are named rather than left to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources