french-admin-mcp

rechercher_entreprise

Search French companies by name, activity, or location using official SIRENE data. Get SIREN, SIRET, address, legal form, creation date, and workforce size.

Instructions

Recherche une entreprise française par nom, activité ou localisation via l'API SIRENE (INSEE). Retourne SIREN, SIRET, adresse du siège, forme juridique, date de création, effectifs. Données officielles et à jour.

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": {
      "recherche": "<recherche>"
    },
    "name": "rechercher_entreprise"
  }
}

Input Schema

Name	Required	Description
`recherche`	Yes	Nom de l'entreprise, mot-clé ou activité à rechercher
`codePostal`	No	Filtrer par code postal (ex : 75001)
`activitePrincipale`	No	Filtrer par code NAF/APE (ex : 62.01Z pour programmation informatique)
`page`	No	Numéro de page (défaut : 1)
`parPage`	No	Nombre de résultats par page (défaut : 5, max : 25)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.2.1Jun 9, 2026

TDQS

A3.7/5.0

Behavior3/5

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

No annotations are provided, so the description must fully disclose behavior. It states returned fields and data freshness but omits details on authentication, rate limits, error handling, or read-only/destructive nature.

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 two concise sentences front-loaded with key purpose, no extraneous words, and efficiently communicates the core functionality.

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

Completeness3/5

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

The description covers basic purpose and returned fields but lacks details on pagination behavior (despite pagination parameters), output format, or error scenarios, which are important for a search tool.

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 adds marginal value by summarizing the search criteria but does not elaborate on parameter syntax or defaults beyond what the schema already provides.

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 clearly states the verb 'Recherche' (searches) and resource 'une entreprise française' via the SIRENE API, distinguishing it from sibling tools like 'details_entreprise' or 'verifier_siret' that handle specific lookups or validity checks.

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?

The description implies usage for searching French companies by name, activity, or location but provides no explicit guidance on when to use alternatives (e.g., 'details_entreprise' for a specific company) or when not to use this tool.

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