Skip to main content
Glama

checkers.fr — entreprises françaises

Rechercher des actes et comptes déposés

rechercher_documents
Read-onlyIdempotent

Recherche les documents déposés au registre national des entreprises : actes (statuts, procès-verbaux d’assemblée, cessions de parts, nominations…) et comptes annuels. Chaque résultat porte un jeton (token) à passer à telecharger_document pour obtenir le PDF. La recherche porte sur la nature de l’acte, pas sur le texte des PDF. Pour les documents d’une seule entreprise, fiche_entreprise les liste déjà. Coût : 0,1 crédit par document renvoyé, rien si aucun.

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

Input Schema

NameRequiredDescriptionDefault
qNoNature de l’acte cherchée (« statuts », « cession de parts », « transfert de siège »).
pageNoPage de résultats (1 par défaut). Les 400 premiers résultats au plus sont accessibles.
sirenNoSIREN de l’entreprise, 9 chiffres.
code_nafNoCodes NAF (APE) de l’activité, séparés par des virgules : « 62.01Z,62.02A ». Un code partiel (« 62 », « 43.2 ») couvre toutes ses sous-classes.
par_pageNoNombre de résultats renvoyés (10 par défaut). Chaque résultat est facturé : n’en demandez pas plus qu’il n’en faut.
departementNoDépartements du siège, séparés par des virgules : « 75,92,2A,974 ».
date_depot_document_maxNoDéposé au plus tard à cette date au format JJ-MM-AAAA ou AAAA-MM-JJ.
date_depot_document_minNoDéposé à partir de cette date au format JJ-MM-AAAA ou AAAA-MM-JJ.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover readOnly, idempotent and non-destructive, so the description correctly spends its space elsewhere: a per-result price (0,1 crédit, nothing if no results) and the token handoff to the download tool. It stops short of describing what each result row contains beyond the token, and does not restate the 400-result access ceiling, which lives in the schema.

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?

Four short sentences, front-loaded with scope, then the token handoff, the limitation, the alternative and finally cost. Every sentence carries information, though the cost sentence could sit slightly later without loss.

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?

For an 8-parameter, zero-required search tool with no output schema, the description covers scope, exclusion, cost and the downstream token workflow. What it omits — the fields present in each result and how filters combine — is modest but not fully covered elsewhere, since no output schema exists.

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 parameter meaning is already fully documented. The description does add one useful interpretive note — that matching is on the nature of the acte rather than document text — which clarifies the intent of the free-text parameter, but it offers no additional syntax or filter-combination guidance.

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 ("Recherche les documents déposés au registre national des entreprises") and enumerates the two document families covered (actes, comptes annuels) with examples of acte types. This clearly separates it from telecharger_document (retrieval) and fiche_entreprise (single-company listing).

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?

Gives explicit routing: use fiche_entreprise when you need documents for one company, and pass the returned token to telecharger_document to get the PDF. It also states a negative scope condition — the search targets the nature of the acte, not the PDF text — which prevents a whole class of misdirected calls.

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