Skip to main content
Glama

TrustyData

by app.trustydata
OverviewDiscussionsAdmin

Fiche d'un établissement ou d'une entreprise

get_company_details
Read-onlyIdempotent

Fiche détaillée d'une entreprise ou d'un établissement français (base SIRENE). Un seul identifiant, deux usages : un SIRET (14 chiffres) renvoie la fiche de CET établissement ; un SIREN (9 chiffres) renvoie celle du SIÈGE de l'entreprise. Structure de la réponse : la racine décrit l'ÉTABLISSEMENT (adresse, activité, effectif, état, conventions collectives applicables à CE site) et le bloc unite_legale décrit l'ENTREPRISE (identité, dirigeants, chiffre d'affaires, TVA). Le niveau de détail dépend du plan : géolocalisation et TVA en Starter, dirigeants et conventions collectives en Growth, finances et procédures collectives en Business. Un champ ABSENT n'est pas une donnée inexistante : il peut relever d'un palier supérieur — son absence ne prouve pas l'inexistence de la donnée. Les dirigeants sont des données personnelles issues du Registre National des Entreprises (INPI) ; chacun porte opposition_prospection — true = cette personne s'est opposée à l'usage de ses données à des fins de prospection commerciale, false = pas d'opposition enregistrée, null = non renseigné (à ne pas lire comme false). C'est le SEUL endroit où cette information est servie. Plan minimum : Discovery.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
company_idYesSIRET (14 chiffres) de l'établissement, ou SIREN (9 chiffres) pour le siège de l'entreprise.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / company_id / description
      Added value: +"SIRET (14 chiffres) de l'établissement, ou SIREN (9 chiffres) pour le siège de l'entreprise."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "type": "object"
+}
  2. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, and the description consistently aligns with these (no contradiction). The description adds significant behavioral context beyond annotations: the distinction between establishment and legal unit in the response structure, the dependency of detail level on plan, and the crucial warning that absent fields do not imply non-existence. It also explains the 'opposition_prospection' field semantics (true/false/null), which is critical for proper interpretation. This is valuable additional context that goes beyond the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is long and dense, covering many aspects, but every sentence delivers substantive information. The key usage logic (SIRET vs SIREN) is front-loaded, which is good, but the latter half introduces complex plan-level details and field-specific interpretation that could overwhelm an agent reading it for the first time. It is not overly verbose, but it could be better organized to prioritize the most actionable points first.

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?

Given the tool's moderate complexity (one parameter, rich response structure with an output schema) and the strong annotations (read-only, open-world, idempotent), the description is quite complete. It explains the response structure, plan-dependent detail levels, the open-world semantics, and the sensitive nature of personal data, which is essential for correct use. It could arguably include a note on rate limits or authorization, but overall it covers the critical context needed for an agent to interpret results correctly.

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 fully describes the only parameter (company_id) with its format and meaning, achieving 100% schema coverage. The description reiterates the SIRET/SIREN duality, which adds a bit of context but largely mirrors the schema. According to the rubric, with high schema coverage, a baseline of 3 is appropriate, and the description does not meaningfully augment the parameter semantics further.

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 clearly states the tool's purpose: retrieving detailed records for French companies or establishments from the SIRENE database. It specifies the exact resource, the two accepted identifier types (SIRET/SIREN), and the corresponding response targets, making its intent unambiguous. It also distinguishes itself from siblings like search_company by focusing on fetching a single record by ID rather than searching.

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 provides clear usage context: it explains the two identifier modes (SIRET for establishments, SIREN for the company's head office), which effectively tells the agent when to use each. It doesn't explicitly name alternatives or when not to use this tool, but the clear scope and single-parameter design make the usage context strong. The sibling tools are all search or address-related, so no further exclusion is needed.

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

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