insourcia

search_directors

Read-onlyIdempotent

Recherche de personnes (dirigeants) a travers toutes les entreprises francaises, par nom de famille.

A la difference de search_companies (qui retourne des ENTREPRISES et accepte dirigeant_nom/dirigeant_prenom comme filtres), search_directors retourne directement des PERSONNES avec leur entreprise de rattachement. Cas d'usage : "toutes les entreprises ou siege un dirigeant nomme DUPONT", cartographie d'un reseau de mandats.

Parametres : nom (REQUIS, nom de famille), prenom (optionnel, desambiguise), role (optionnel, ex "President", "Gerant", "Administrateur"). Par defaut seuls les mandats actifs ; include_inactive=true pour inclure les anciens mandats.

Reponse : data[] = personnes { nom, prenom, civilite, role, role_description, date_naissance, annee_naissance, lieu_naissance, type_personne, linkedin_url, entreprise { siren, denomination, ville, departement, code_ape } }. linkedin_url n'est present que si un profil a ete apparie avec certitude (plan pro) ; son absence est le cas courant, pas une anomalie. pagination { total (nb entreprises matchees), limit, returned }.

Homonymes : un meme nom+prenom recouvre souvent plusieurs personnes distinctes. date_naissance est le champ qui les distingue : deux dates differentes = deux personnes ; date absente = identite non confirmee ; meme date = meme personne. La date est diffusee au MOIS (jour normalise a 01), conformement au regime de diffusion du registre : deux personnes nees le meme mois restent indistinguables.

Pour lister TOUTES les entreprises d'une personne donnee une fois sa date de naissance connue, enchainer avec search_director_companies (nom + prenom + date_naissance). Pour la fiche complete d'un dirigeant d'une entreprise donnee, utiliser get_directors avec le SIREN.

Input Schema

TableJSON Schema

Name	Required	Description
`nom`	Yes	Nom de famille du dirigeant recherche (requis).
`role`	No	Role/qualite (optionnel), ex: 'President', 'Gerant', 'Administrateur'.
`limit`	No	Nombre d'entreprises a scanner (defaut 20, max 50).
`prenom`	No	Prenom (optionnel) pour desambiguiser les homonymes.
`include_inactive`	No	Inclure les mandats inactifs (defaut: false).

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	No
`_user_plan`	No
`pagination`	No
`_credits_remaining`	No
`_quota_remaining_month`	No
`_quota_remaining_today`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 22, 2026
- addedOutput schema / properties / _credits_remaining
```
Added value: +{
+  "type": "number"
+}
```
Changed1 schema field changedSep 22, 2026
- removedOutput schema / properties / _credits_remaining
```
Removed value: -{
-  "type": "number"
-}
```
Changed1 schema field changedSep 22, 2026
- addedOutput schema / properties / _credits_remaining
```
Added value: +{
+  "type": "number"
+}
```
Changed1 schema field changedSep 22, 2026
- removedOutput schema / properties / _credits_remaining
```
Removed value: -{
-  "type": "number"
-}
```
Changed1 schema field changedSep 22, 2026
- addedOutput schema / properties / _credits_remaining
```
Added value: +{
+  "type": "number"
+}
```
Changed1 schema field changedSep 22, 2026
- removedOutput schema / properties / _credits_remaining
```
Removed value: -{
-  "type": "number"
-}
```
Changed1 schema field changedSep 22, 2026
- addedOutput schema / properties / _credits_remaining
```
Added value: +{
+  "type": "number"
+}
```
Changed1 schema field changedSep 22, 2026
- removedOutput schema / properties / _credits_remaining
```
Removed value: -{
-  "type": "number"
-}
```
Changed1 schema field changedSep 22, 2026
- addedOutput schema / properties / _credits_remaining
```
Added value: +{
+  "type": "number"
+}
```
Changed1 schema field changedSep 22, 2026
- removedOutput schema / properties / _credits_remaining
```
Removed value: -{
-  "type": "number"
-}
```
Changed1 schema field changedSep 22, 2026
- addedOutput schema / properties / _credits_remaining
```
Added value: +{
+  "type": "number"
+}
```
Changed1 schema field changedSep 22, 2026
- removedOutput schema / properties / _credits_remaining
```
Removed value: -{
-  "type": "number"
-}
```
Changed1 schema field changedSep 15, 2026
- addedOutput schema / properties / _credits_remaining
```
Added value: +{
+  "type": "number"
+}
```
Changed1 schema field changedSep 14, 2026
- changedOutput schema / properties / pagination / additionalProperties
```
Previous value: -falseNew value: +{}
```

Changed3 schema fields changedSep 3, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

removedInput schema / properties / context

Removed value: -{
-  "description": "Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): \"Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization.\"",
-  "type": "string"
-}

changedInput schema / required

Previous value: -[
-  "nom",
-  "context"
-]New value: +[
+  "nom"
+]

Changed3 schema fields changedSep 1, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```

addedInput schema / properties / context

Added value: +{
+  "description": "Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): \"Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization.\"",
+  "type": "string"
+}

changedInput schema / required

Previous value: -[
-  "nom"
-]New value: +[
+  "nom",
+  "context"
+]

First observedSep 1, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already mark this as read-only, idempotent, and non-destructive. The description adds substantial behavioral detail beyond that: the linkedin_url is only present under a certain pro match and its absence is normal, date of birth is diffused at month granularity, and homonym identity is resolved via date_naissance. These details materially affect how an agent interprets results.

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?

Although the description is long, every section earns its place: differentiation from siblings, parameter semantics, response shape with edge cases, homonym guidance, and follow-up tool routing. The structure is organized into clear paragraphs and the most decision-relevant scoping sentence comes first.

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?

Given the tool's complexity—homonym handling, optional fields, cross-tool workflows, and nuanced response semantics—the description is complete. It covers return fields, missing-data cases, pagination meaning, defaults, and what to call next, so an agent has everything needed to invoke and interpret this tool 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?

The input schema covers all parameter names and basics at 100%, so the baseline is 3. The description adds meaning beyond the schema: prenom 'desambiguise', role examples, and the default behavior of active mandates only with include_inactive=true to broaden. It does not add anything for 'limit' that the schema already states, so a 4 rather than 5 is appropriate.

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 states a precise verb-resource pair: it searches for persons (directors) across all French companies by family name. It also explicitly contrasts itself with search_companies ('retourne des ENTREPRISES') and gives concrete use cases, so an agent can cleanly distinguish it from 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?

The description gives explicit when-to-use guidance and names sibling tools for related tasks: search_companies for companies, search_director_companies for all companies of a known person, and get_directors for the full record by SIREN. It also states defaults and the role of include_inactive, leaving no ambiguity about when to invoke this tool versus alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All insourcia tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?