get_enterpriseFetch a single legal unit with all its establishments by SIREN (9 digits).
| Name | Required | Description | Default |
|---|---|---|---|
| siren | Yes | 9-digit SIREN identifier |
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | Current page (always 1) | |
| results | No | Array with single legal unit (or empty if not found) | |
| per_page | No | Results per page (always 1) | |
| total_results | No | Total number of matching results (0 or 1) |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Input schema / examplesPrevious value: -[
- {
- "siren": "123456789"
- }
-]New value: +[
+ {
+ "siren": "552032534"
+ }
+]Input schema / examplesAdded value: +[
+ {
+ "siren": "123456789"
+ }
+]Output schema / (root)Previous value: -nullNew value: +{
+ "properties": {
+ "page": {
+ "description": "Current page (always 1)",
+ "type": "number"
+ },
+ "per_page": {
+ "description": "Results per page (always 1)",
+ "type": "number"
+ },
+ "results": {
+ "description": "Array with single legal unit (or empty if not found)",
+ "items": {
+ "properties": {
+ "address": {
+ "description": "Registered address",
+ "type": "string"
+ },
+ "ape": {
+ "description": "APE/NAF activity code",
+ "type": "string"
+ },
+ "city": {
+ "description": "City name",
+ "type": "string"
+ },
+ "denomination": {
+ "description": "Legal unit name",
+ "type": "string"
+ },
+ "departement": {
+ "description": "French département code",
+ "type": "string"
+ },
+ "dirigeants": {
+ "description": "Directors and managers",
+ "items": {
+ "properties": {
+ "fonction": {
+ "description": "Role/title",
+ "type": "string"
+ },
+ "nom": {
+ "description": "Director name",
+ "type": "string"
+ },
+ "prenom": {
+ "description": "Director first name",
+ "type": "string"
+ }
+ },
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "etablissements": {
+ "description": "All registered establishments",
+ "items": {
+ "properties": {
+ "address": {
+ "description": "Establishment address",
+ "type": "string"
+ },
+ "city": {
+ "description": "City name",
+ "type": "string"
+ },
+ "enseigne": {
+ "description": "Trading name",
+ "type": "string"
+ },
+ "etat_administratif": {
+ "description": "Status (A=active, R=closed)",
+ "type": "string"
+ },
+ "postal_code": {
+ "description": "5-digit postal code",
+ "type": "string"
+ },
+ "siret": {
+ "description": "14-digit SIRET identifier",
+ "type": "string"
+ }
+ },
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "etat_administratif": {
+ "description": "Administrative status (A=active, R=radiated)",
+ "type": "string"
+ },
+ "labels": {
+ "description": "RGE eco-labels or certifications",
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ },
+ "postal_code": {
+ "description": "5-digit postal code",
+ "type": "string"
+ },
+ "sigle": {
+ "description": "Abbreviated name or acronym",
+ "type": "string"
+ },
+ "siren": {
+ "description": "9-digit SIREN identifier",
+ "type": "string"
+ },
+ "tranche_effectif_salarie": {
+ "description": "Employee count band",
+ "type": "string"
+ }
+ },
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "total_results": {
+ "description": "Total number of matching results (0 or 1)",
+ "type": "number"
+ }
+ },
+ "type": "object"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, conveying safety. The description adds that the tool returns 'all its establishments', which clarifies the scope of the response. It provides useful context beyond annotations without contradiction.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single sentence that is front-loaded and efficient. Every word adds value without redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given low complexity (1 required param, no enums, output schema present), the description is complete. It covers the tool's purpose, parameter format, and return scope (legal unit with establishments). The output schema documents the return structure.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% with the siren parameter described as '9-digit SIREN identifier'. The description reinforces this by mentioning 'by SIREN (9 digits)', adding slight value. Baseline 3 with a bump for explicit format emphasis.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the verb ('Fetch a single legal unit with all its establishments') and the resource ('by SIREN (9 digits)'). It is specific and distinguishes from sibling tools like search or resolve, as it is a direct fetch by identifier.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explicitly indicates when to use this tool: when you have a 9-digit SIREN and need a single legal unit with establishments. The format constraint (9 digits) is clearly stated, and the sibling tools are mostly unrelated, so no negative guidance is needed.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.