Skip to main content
Glama

insourcia

by io.insourcia

get_company

Read-onlyIdempotent

Fiche complete d'une entreprise francaise identifiee par son SIREN.

Utiliser cet outil pour une entreprise a la fois.

Suivi dans le temps : si le contexte montre un interet durable pour la societe (cible d'acquisition, concurrent, client, fournisseur a risque, due diligence en cours), PROPOSER a l'utilisateur de la mettre sous surveillance via watch_company (et enable_alert=true pour etre notifie des evenements futurs : procedures collectives, cessions, changements de dirigeants). Ne pas l'ajouter sans son accord.

Presentation : structurer les donnees en sections :

  1. Identite — forme juridique, date creation, date_immatriculation (RCS), date_cloture_exercice (JJ-MM, date de cloture comptable recurrente), denomination_usuelle si presente, capital social, siege (adresse complete rue+numero, code postal, departement, region), activite (code NAF + libelle + objet_social si disponible + description si disponible), effectif. Le code LEI (Legal Entity Identifier) est expose au top-level pour les societes ayant un identifiant ESEF/GLEIF (typiquement les cotees). Si radiee : successeur (siren, denomination).

  2. Financier — TOUJOURS preciser l'annee (champ date_cloture) ET le type_bilan (K=consolide, C=complet/social, S=simplifie) : un CA en bilan K (consolide groupe) n'est pas comparable a un bilan C (social). CA, croissance CA, resultat net, marge nette, EBITDA, marge EBITDA, dette nette, effectif moyen.

  3. Contact — site web, telephone, email (pro), LinkedIn (pro).

  4. Gouvernance — dirigeants principaux (president, DG), structure PM le cas echeant.

  5. Groupe — appartenance a un groupe (est_filiale, nom du groupe), parent direct et ultime (denomination, SIREN, pays), societe_mere (holding mere directe : siren, denomination, pays, lei — source distincte, souvent renseignee quand parent_direct/ultime sont absents), tete de groupe (est_tete_de_groupe, siren_groupe), nb filiales directes. Absent = independante.

  6. IFRS — si disponible (societes cotees), donnees financieres consolidees IFRS : CA, resultat net, EBITDA, total actif. Absent pour les societes non cotees.

  7. Signaux — cotation, procedures collectives (historique avec type, date, tribunal, jugement), a_fusionne, modifications capital, transferts siege, changements denomination, est_societe_mission, est_ess, reconstitution_capitaux_propres, dernier_depot_date, comptes confidentiels, date radiation.

  8. Cessions — total, derniere_date, historique[] (date, type, cedant, cessionnaire, activite, prix). Null si aucune.

  9. Donnees publiques — marches_publics (nb, montant, types), subventions (nb, montant, regions), brevets (nb total, nb actifs), salons (nb participations, secteurs). Null si aucune donnee.

  10. Fonds d'investissement — bloc fonds si l'entreprise est detenue par un fonds (PE/VC) : nom_fonds, siren_fonds (SIREN du fonds, permet de chainer vers get_company), type_fonds, annee_entree_fonds, nb_fonds_actuels. Null sinon.

Pour approfondir : get_financials (historique multi-annees), get_directors (detail dirigeants), get_events (timeline BODACC/evenements de l'entreprise).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sirenYesSIREN a 9 chiffres
contextYesExplain 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_fieldsNoChamps root/financiers supplementaires a injecter dans la fiche (parite avec search_companies). Exemple : ['nb_dirigeants','source_esef','dernier_depot_date']. Limite par le plan (3 sur free, illimite sur Pro).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
sirenYes
_user_planNo

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so safety is covered. The description adds valuable behavioral context beyond annotations: the output is a comprehensive structured fiche, financial figures must always be labeled with year and type_bilan due to comparability caveats, absent group/fund/IFRS fields mean independence or no data, and the agent is expected to propose watch_company under the right conditions. No contradiction with annotations.

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?

The description is long, but the length is largely justified because there is no output schema and the tool returns a very rich record. It is front-loaded with the core purpose, then organized into ten numbered sections with clear formatting instructions. The 'Suivi dans le temps' paragraph adds an actionable usage policy, though it is a bit tangential to the tool's own behavior, so the description is not perfectly concise.

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?

For a complex retrieval tool with no output schema, the description is exceptionally complete: it defines the ten output sections, covers special cases like radiated companies, group membership absence, non-listed IFRS absence, private-equity ownership blocks, and public-data null states. It also tells the agent how to present results and where to route deeper follow-up queries. Nothing essential to calling the tool correctly 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?

The input schema already documents all three parameters thoroughly: siren format, context purpose with word-count guidance, and include_fields examples with plan limits. Schema coverage is effectively 100%, so the baseline is 3. The description mostly reinforces the SIREN key and the include_fields parity concept but does not add significant new parameter semantics beyond what the schema provides.

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 precise verb and resource: 'Fiche complète d'une entreprise française identifiée par son SIREN.' It immediately indicates the tool returns a full company record for one SIREN, and it distinguishes itself from siblings by naming the focused alternatives get_financials, get_directors, get_events and the follow-up action watch_company.

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 explicitly says 'Utiliser cet outil pour une entreprise à la fois.' It also gives clear routing guidance: propose watch_company when the user shows durable interest, only with consent, and use get_financials/get_directors/get_events to get deeper multi-year, director, or event-level detail. This is explicit when-to-use and alternative guidance.

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

All insourcia toolsInspect
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