Skip to main content
Glama

checkers.fr — entreprises françaises

Fiche d’une entreprise

fiche_entreprise
Read-onlyIdempotent

Fiche complète d’une entreprise française : identité (forme, capital, activité, date de création, TVA), siège et établissements, dirigeants en fonction et passés, chiffres clés par exercice, procédures collectives, annonces BODACC, actes et comptes déposés (chacun avec le jeton à passer à telecharger_document), et le lien vers sa page checkers.fr. Désignez l’entreprise par siren, siret, ou (pour savoir qui est derrière un site ou une adresse) par domaine (« exemple.fr ») ou email (« contact@exemple.fr » ; les messageries grand public comme gmail.com sont refusées). Sans SIREN, appelez d’abord suggerer_entreprises (gratuit) ou rechercher_entreprises. Coût : 1 crédit, plus les options renseignées (sites_internet +1, telephone +3, email +3, lien_linkedin +3, marques +1, appels_offres_gagnes et appels_offres_lances +2).

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

Input Schema

NameRequiredDescriptionDefault
emailNoAdresse e-mail professionnelle : l’entreprise est retrouvée par son domaine.
sirenNoSIREN de l’entreprise, 9 chiffres.
siretNoSIRET d’un établissement, 14 chiffres.
domaineNoSite internet de l’entreprise, sans http (« doctolib.fr »).
champs_supplementairesNoDonnées payantes à ajouter, facturées seulement si elles existent : sites_internet, telephone, email, lien_linkedin (relevés sur le site de l’entreprise), marques (déposées à l’INPI), appels_offres_gagnes et appels_offres_lances (marchés publics).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnlyHint/idempotent/destructive=false, so the bar is lower, and the description still adds substantial behavior: the credit cost, per-option surcharges, and the rule that optional paid fields are billed only when data exists. It also discloses the public-email-domain rejection, a constraint that would otherwise fail silently at call time.

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?

It is front-loaded (what you get, then how to identify the company, then cost) with no filler sentences. It is dense to the point of being a single packed paragraph with heavy parentheticals, which slightly hurts scannability, but nothing is redundant.

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?

With no output schema, the description compensates by enumerating the returned sections and the document-token convention for telecharger_document, and all five parameters are covered by the schema plus description. For a read-only lookup with full schema coverage, an agent has everything needed to call it correctly.

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 100%, so baseline is 3, but the description goes beyond the schema by attaching a price to each champs_supplementaires option (telephone +3, marques +1, etc.) and by explaining the rationale (data relevé sur le site, INPI, marchés publics). The email restriction on consumer providers is also meaning the schema does not carry.

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 opens with a precise verb+resource ('Fiche complète d'une entreprise française') and then enumerates exactly what the record contains: identity, siège/établissements, dirigeants, key figures per fiscal year, procédures collectives, BODACC notices, deposited acts and accounts, plus the checkers.fr link. That enumeration, plus the explicit hand-off of document tokens to telecharger_document, makes it clearly distinguishable from recherche/suggestion siblings.

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?

It states the accepted lookup keys (siren, siret, domaine, email) and adds a prerequisite for the no-SIREN case: call suggerer_entreprises (free) or rechercher_entreprises first. It also gives an exclusion rule (consumer mail domains like gmail.com are refused) and the full pricing model including per-option costs, so an agent can decide whether to invoke it and with which options.

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