Skip to main content
Glama

Lexou · droit français

Fiche d'une entreprise et procédures collectives

rechercher_entreprise
Read-onlyIdempotent

Identité d'une entreprise française (SIREN, état actif ou cessé, forme juridique, dirigeant principal, conventions collectives, chiffres publiés) d'après l'annuaire officiel des entreprises, et ses procédures collectives publiées au BODACC. À utiliser avec un nom ou un SIREN. Pas pour les bénéficiaires effectifs.

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

Input Schema

NameRequiredDescriptionDefault
nom_ou_sirenYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuine context beyond that: two authoritative sources (the official business directory and BODACC) and the fact that both active and ceased companies are covered. It does not say what happens when no match is found or whether multiple matches may be returned.

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?

Two compact sentences with no filler, and the returned-data scope is front-loaded ahead of the usage constraint. The parenthetical field list is dense but every element describes concrete returned content, so nothing is wasted.

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 no output schema, the description does the work of explaining what comes back, and it names the underlying sources for both the identity data and the insolvency procedures. Remaining gaps are the response shape and no-match behavior, which are secondary for a single-parameter lookup.

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?

Schema coverage is 0% and the single parameter is only typed as a 2-120 character string, so the description carries the burden. 'À utiliser avec un nom ou un SIREN' meaningfully tells the agent that either a company name or a SIREN identifier is accepted, which the schema does not convey.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific resource (the identity of a French company) and enumerates the fields returned: SIREN, active/ceased status, legal form, main director, collective agreements, published figures, plus collective procedures from BODACC. It also explicitly excludes beneficial owners, which narrows the scope. It stops short of routing against any named sibling, so 4 rather than 5.

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?

'À utiliser avec un nom ou un SIREN' states the accepted input condition, and 'Pas pour les bénéficiaires effectifs' is an explicit when-not. No alternative tool is named for the excluded case or for related lookups, so the guidance is clear but incomplete.

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