Skip to main content
Glama

fr_company

Look up French companies by name, SIREN, or SIRET to retrieve official legal name, HQ address, NAF code, status, and creation date from Sirene open data.

Instructions

French company lookup (SIREN/SIRET/name) from the official open-data Sirene base (recherche-entreprises.api.gouv.fr, Licence Ouverte Etalab). Returns legal name, SIREN, HQ address, NAF code, status, creation date, directors when public. Costs 0.005 USDC on Base per successful call (x402). Without a payment key this tool returns the 402 challenge.

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": "fr_company"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesCompany name, SIREN (9 digits) or SIRET (14 digits)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it names the upstream API and license, enumerates the returned fields, discloses that directors are only included 'when public', and explains the x402 payment model and the 402-challenge failure mode. It omits rate limits, pagination, and no-match behavior, which keeps it below 5.

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?

Two sentences, both front-loaded with the highest-value information: what the tool is and where data comes from first, then the return shape and cost/payment precondition. No filler or redundant restatement of the title.

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 read lookup with no output schema, the description supplies the return field set, data provenance for trustworthiness, and the payment/failure model. Nothing an agent needs in order to decide to call it, or to interpret a 402 response, is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is a single required parameter and the schema already documents it fully (coverage 100%), so the description only needs to reinforce it; noting the accepted forms (name, 9-digit SIREN, 14-digit SIRET) matches rather than extends the schema. With one param and full coverage, this is adequate without adding new semantics.

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 ('French company lookup') plus the accepted identifier forms (SIREN/SIRET/name) and the authoritative data source. The 'French' qualifier and the Sirene base reference let an agent distinguish it from fi_company, no_company, and uk_company without opening another schema.

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 country/registry framing makes the applicable context clear, and the payment note ('costs 0.005 USDC on Base per successful call... without a payment key this tool returns the 402 challenge') is a concrete precondition an agent must check before calling. It stops short of explicitly routing to alternatives such as kyb_check_fr or fr_legal_status, so no exclusions are stated.

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