Skip to main content
Glama

checkers.fr — entreprises françaises

Retrouver une entreprise par son nom

suggerer_entreprises
Read-onlyIdempotent

Autocomplétion : à partir d’un nom (même partiel, même approximatif), d’un SIREN ou d’un SIRET, renvoie les entreprises qui correspondent le mieux avec leur SIREN, leur forme, leur ville et leur activité. À appeler en premier quand l’utilisateur nomme une entreprise sans donner son SIREN, pour lever l’ambiguïté avant fiche_entreprise. Coût : Gratuit, même sans compte, jusqu’à 100 appels par jour, puis 0,1 crédit par suggestion.

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": {
      "q": "<q>"
    },
    "name": "suggerer_entreprises"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesNom de l’entreprise, début du nom, SIREN ou SIRET.
longueurNoNombre de suggestions (10 par défaut).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description still adds real value beyond them: it discloses the ranking behavior ('correspondent le mieux'), the returned fields, and a concrete cost/limit model (free to 100 calls/day, then 0.1 credit per suggestion). It does not describe ordering ties or empty-result behavior, keeping it short of a 5.

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?

Three sentences, each doing distinct work: capability and return fields first, routing guidance second, cost model last. Nothing is repeated from the schema or annotations, and the most decision-relevant information is front-loaded.

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 naming the fields returned (SIREN, forme, ville, activité). Combined with input forms, the fuzzy-matching hint, the routing rule, and the credit cost for a tool that consumes paid credits, 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 the baseline is 3. The description nevertheless adds meaning by stating the name may be 'même partiel, même approximatif', which signals fuzzy/typo-tolerant matching that the schema's parameter text ('début du nom') does not convey.

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 specific verb and resource ('Autocomplétion' on entreprises) and enumerates both the accepted input forms (partial/approximate name, SIREN, SIRET) and the returned fields (SIREN, forme, ville, activité). This is clearly distinguishable from siblings like fiche_entreprise or rechercher_entreprises.

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 explicitly when to call it ('en premier quand l'utilisateur nomme une entreprise sans donner son SIREN') and why ('pour lever l'ambiguïté avant fiche_entreprise'), naming the sibling it precedes. No inference is required to pick this tool for a name-only lookup.

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