Skip to main content
Glama

fr_directors

Read-only

Directors declared at the French registry (RNE), for one company or a LIST — sirens=[…] (max 100) returns {entreprises, count, obtenues, en_echec, erreurs, not_found, synthese}, one entry per SIREN in input order.

⚠️ An empty dirigeants has THREE meanings, told apart by registre: the SIREN is unknown (error: "not_found"), the legal form is not registered so it declares nobody (hors_registre — association, commune: the emptiness says nothing about the company), or the company is registered with nobody on file (attendu). Never read an empty list as "no director" without reading registre. personnes_physiques counts the NAMED natural persons — a company whose only director is another company scores 0.

⚠️ count counts the records OBTAINED, not the lines returned — en_echec and erreurs name what is missing, at the top level. ⚠️ An error other than not_found is an upstream failure, not a fact about the company — and it is RETRYABLE.

A batch of 50 where 21 calls failed returns count: 29, en_echec: 21 and names those 21 SIRENs in erreurs — at the top level, like not_found, because a hundred-line list is not re-read to find them. Reading count and not_found alone used to say "50 records, none missing" while 21 companies silently dropped out of the deliverable. The batch paces itself and retries the upstream quota (429, honouring Retry-After), so what reaches you has already been given a second chance; a SIREN still in erreurs says the upstream is busy, never that the company has no director. Ask for those SIRENs again, later or in a smaller batch.

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

Input Schema

NameRequiredDescriptionDefault
_orgNoOrg (id) de CET APPEL. `oto_list_orgs()`.
sirenNoSIREN number (9 digits) — single-company mode.
_groupNoÉquipe (id) de CET APPEL, sous son org parente.
sirensNolist of SIREN numbers (max 100) — batch mode. Give one OR the other, not both.
_run_idNoOBLIGATOIRE à chaque appel dès `run_start` ou `data_claim_next` : sans lui, l'écriture sur une ligne réservée est refusée. Hérité seulement si le serveur tient un run actif — n'y compte pas.
_projectNoProjet (id) de CET APPEL — jeton PRIMAIRE. `oto_project(op='list')`.
_instanceNoInstance de connecteur PRÉCISE (un credential exact). `oto_instance(op='list')`.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=true; the description goes far beyond by decoding the three meanings of an empty `dirigeants` via `registre` (not_found / hors_registre / attendu), explaining that `count` counts records obtained rather than lines returned, and stating that non-`not_found` errors are retryable upstream failures. It also discloses internal pacing and 429/Retry-After retry behavior, which no annotation conveys.

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?

Purpose and return shape are front-loaded, and the ⚠️ markers make the critical caveats scannable. Some material is defensive narrative rather than instruction — the aside about what 'reading count and not_found alone used to say' is historical justification an agent does not need — which keeps it from a 5.

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?

There is no output schema, so the description carries the full burden and does: it enumerates the return keys (`entreprises, count, obtenues, en_echec, erreurs, not_found, synthese`) and explains how to read the ambiguous ones. For a batch tool with failure modes, nothing an agent needs to interpret a response correctly is missing.

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, but the description adds real meaning: `sirens` is capped at 100, results come back one entry per SIREN in input order, and the two modes are mutually exclusive. It does not elaborate on the `_org`/`_group`/`_run_id` context parameters, but those are documented in the schema.

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 ('Directors declared at the French registry (RNE)') and immediately distinguishes the two modes: single company via `siren` or a LIST via `sirens=[…]` (max 100). An agent knows exactly what it retrieves and in what shape, without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description makes the single-vs-batch choice clear and warns to re-query SIRENs left in `erreurs` later or in a smaller batch, which is genuine usage guidance. However, it never names an alternative sibling (e.g. fr_get, fr_siret, fr_stock_siege) or says when a different tool is the better pick, so routing guidance is only implied.

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