Skip to main content
Glama

Lexou · droit français

Vérifier un agrément bancaire ou d'assurance (ACPR)

verifier_agrement_acpr
Read-onlyIdempotent

Cherche une banque, un établissement de paiement ou de monnaie électronique, une entreprise d'investissement, un organisme de financement, un agent ou un assureur dans le registre officiel de l'Autorité de contrôle prudentiel et de résolution (REGAFI et assurances), par nom ou SIREN. Rend le statut, la catégorie, les activités autorisées et les passeports européens. Pas pour les intermédiaires immatriculés à l'ORIAS, ni pour les listes noires de l'AMF.

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

Input Schema

NameRequiredDescriptionDefault
domaineNo
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.1/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, open-world and non-destructive behavior, so the bar is lower. The description adds real value beyond them by disclosing what the call returns (statut, catégorie, activités autorisées, passeports européens) and naming the underlying registries. It does not say what happens when no match is found, which is the main residual gap.

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?

Three sentences, front-loaded with the action and scope, then return content, then exclusions. The long enumeration of entity types is verbose but earns its place by defining coverage. No filler or repetition.

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 a two-parameter lookup with no output schema, the description supplies the source registries, the accepted inputs, the returned fields and the boundaries. Only edge behavior (no-result handling, partial name matching) is left unstated, which is minor.

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 0%, so the description must carry the parameter burden. "par nom ou SIREN" usefully explains that nom_ou_siren accepts two formats, but the domaine parameter (enum banque/assurance) is never mentioned, so half the parameters are only documented by the schema itself.

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 names a specific verb ("Cherche ... dans le registre officiel") plus the exact resource (registre ACPR / REGAFI et assurances) and enumerates the entity types covered (banques, établissements de paiement, entreprises d'investissement, agents, assureurs). It also states the search keys (nom ou SIREN), so an agent can distinguish it from any other registry lookup immediately.

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?

Explicit exclusions are given: not for ORIAS-registered intermediaries and not for AMF blacklists, the latter clearly routing to the sibling verifier_listes_noires_amf. The positive conditions (regulated ACPR-supervised entities) are clear from the entity enumeration. It stops short of naming an alternative for the ORIAS case, which keeps it at 4 rather than 5.

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