insourcia

get_directors

Read-onlyIdempotent

Detail des dirigeants d'une entreprise avec structure hierarchique.

Retourne les dirigeants classes par importance (decisionnaires en premier). Deux types d'entrees :

PP (personne physique) : nom, prenom, role, annee de naissance, date_debut_mandat, date_fin_mandat
PM (personne morale) : denomination, SIREN, role, date_debut_mandat, date_fin_mandat, avec un tableau representants[] listant les personnes physiques qui la representent (nom, prenom, role dans la PM, dates de mandat)

Inclut les commissaires aux comptes (role="CAC") avec leur date de debut/fin de mandat. Utile pour identifier le mandataire actif vs sortant.

Par defaut, seuls les mandataires actifs sont retournes. Utiliser include_inactive=true pour inclure l'historique.

Utiliser cet outil pour une entreprise a la fois.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Nombre de resultats (defaut 20, max 100)
`siren`	Yes	SIREN a 9 chiffres
`offset`	No	Pagination (defaut 0)
`context`	Yes	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."
`include_inactive`	No	Inclure les mandataires inactifs (historique). Defaut: false

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	Yes
`siren`	Yes
`message`	No
`_user_plan`	No
`pagination`	No
`denomination`	No

TDQS

A4.5/5.0

Behavior5/5

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

Beyond the readOnly/idempotent annotations, the description discloses sorting by importance, default filtering to active mandataires, inclusion of CAC roles with mandate dates, and nested representants[] for PM entities. This gives the agent a clear expectation of what the tool returns and how it behaves.

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?

The description is well-structured with bolded entity types, bullet-like field lists, and a clear flow from purpose to output shape to defaults to usage guidance. Every sentence adds useful information without redundancy.

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?

Combined with the output schema and annotations, the description is complete for selecting and invoking the tool: it specifies required context (single company), return structure, filtering behavior, and how to include history. Nothing essential is missing.

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 100%, so the baseline is 3. The description reinforces include_inactive semantics and default behavior, but adds little beyond what the schema already states for parameters like siren, limit, and offset.

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 'Detail des dirigeants d'une entreprise avec structure hierarchique' and specifies that it returns directors sorted by importance, with PP and PM entity shapes. This clearly distinguishes it from sibling search tools by anchoring it to a single company via SIREN.

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?

The description gives clear usage context: 'Utiliser cet outil pour une entreprise a la fois' and explains the active/inactive default behavior via include_inactive. It does not explicitly name alternatives or state when not to use sibling tools, but the single-company constraint and SIREN requirement provide solid guidance.

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

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.3/5.0

Disambiguation4/5

Most tools have clearly distinct resource+action purposes, and the descriptions explicitly contrast near-neighbor tools like search_companies vs resolve_companies and get_events vs search_events. The only real risk is the trio of director-oriented tools, especially search_director_companies vs search_companies with dirigeant filters, which requires careful reading to avoid misselection.

Naming Consistency5/5

All 18 tools follow a consistent snake_case verb_noun pattern: search_, get_, list_, create_, watch_, unwatch_, mark_, resolve_. Singular names are used for single-entity actions and plural for list/search operations, making the pattern predictable. There is no camelCase, vague verb, or style mixing.

Tool Count4/5

18 tools is slightly above the ideal 10-15 range, but the count is justified by the broad domain covering search, company intelligence, watchlists, and news. Each tool appears to earn its place, and there are no obvious stubs or redundant duplicates. It feels a bit heavy but not bloated.

Completeness3/5

The company intelligence surface is very complete: search, deep company data, financials, directors, group graphs, events, and credit risk are all covered. Watchlists also have full add/remove/list coverage, but saved searches have a notable lifecycle gap—create and list exist, yet there is no update, delete, or alert-toggle for existing saved searches, creating a management dead end.

Resources

Need Help?