Skip to main content
Glama

Open data: clinical trials, EU tenders, companies, fuel prices

French Company Search (Recherche d'entreprises, Sirene)

fr-company-search
Read-onlyIdempotent

Search France's official company register by NAF activity code, département, headcount band and status, and get typed legal-entity records with head-office address, coordinates and company size. Read from recherche-entreprises.api.gouv.fr when called. Each result: siren, siret_head_office, name, legal_name, naf_code, legal_form_code, address, postcode, city, departement, lat, lon, creation_date, headcount_band, company_category, establishments_total, establishments_open, status. Needs a RapidAPI key for this API (https://rapidapi.com/IanGregory/api/clinical-trials-eu-tenders-open-data-api), sent as the X-RapidAPI-Key header; the listing has a free plan.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "fr-company-search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoAt most this many results (default 100).
departementNoDépartement code of the head office, e.g. 75 Paris, 69 Rhône, 2A Corse-du-Sud. Leave empty for all of France. Example: "75".
etat_administratifNoA = active companies, C = ceased companies. Example: "A".
activite_principaleNoMain activity code (NAF rev. 2) of the company, e.g. 62.01Z (computer programming), 56.10A (restaurants), 47.11D (supermarkets). Example: "62.01Z".
tranche_effectif_salarieNoINSEE headcount band: 00 (0), 01 (1-2), 02 (3-5), 03 (6-9), 11 (10-19), 12 (20-49), 21 (50-99), 22 (100-199), 31 (200-249), 32 (250-499), 41 (500-999), 42 (1000-1999), 51 (2000-4999), 52 (5000-9999), 53 (10000+). Leave empty for any. Example: "11".

Output Schema

NameRequiredDescriptionDefault
countYeshow many results came back
itemsYesthe results, one object each
partialNosome of the source's requests failed: the results are incomplete
productNo
sourcesNowhere the data came from: each source's name, licence and the attribution to show with it
fetched_atNowhen the source was read (Unix seconds)
truncated_fromNothe answer was cut to fit: this many results came back in all

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), and the description goes beyond them with genuinely useful operational facts: it hits a live external API at call time, it requires a RapidAPI key passed as X-RapidAPI-Key, and a free plan exists. Deduction because the supplied RapidAPI listing URL points at a 'clinical-trials-eu-tenders' API rather than a French company register, which risks sending an agent to the wrong credential source.

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

Conciseness3/5

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

Front-loaded with the purpose, which is good, but then spends a long clause enumerating seventeen result fields that an output schema already defines, duplicating structured data instead of adding insight. The trailing auth/pricing sentence is valuable, yet the sentence structure is a run-on chain rather than cleanly separated purpose / behavior / auth blocks.

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?

With rich annotations, a full output schema and 100% parameter coverage, the description supplies the pieces the structure cannot: live-data source, authentication requirement and header, and free-tier availability. Nearly complete, but the mismatched RapidAPI listing URL and the absence of any default-scope note (how many results come back by default) leave a small gap.

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 the baseline is 3; each parameter already has examples and enum explanations in the schema. The description restates the filter axes (NAF, département, headcount band, status) but omits the `limit` parameter and adds no format or interaction detail beyond what the schema supplies.

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?

Opens with a specific verb+resource ("Search France's official company register") and names the four filter axes (NAF code, département, headcount band, status) plus what comes back (typed legal-entity records with address/coordinates/size). The domain is unmistakably distinct from every sibling (app-store, clinical-trials, fuel, scholarly, TED tenders), so no sibling disambiguation is needed.

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

Usage Guidelines3/5

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

Usage is only implied: the filters signal 'look up companies matching these criteria', and "Leave empty for all of France"-style guidance lives in the schema, not the description. There is no statement of when to prefer this over any alternative, no note on filter combinations that must accompany each other, and no exclusion cases. Adequate for a self-evident search tool with unrelated siblings, but not more.

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