Entreprises Fr

Search

search

Read-onlyIdempotent

Full-text search across French legal units. Matches name, sigle, director names, addresses. Returns SIREN, denomination, establishments, sector code (APE/NAF), and basic financials.

Input Schema

TableJSON Schema

Name	Required	Description
`ape`	No	APE/NAF activity code (e.g. "6201Z" software dev)
`page`	No	1-based page (default 1)
`query`	Yes	Free-text — name / director / address
`per_page`	No	Page size, 1-25 (default 10)
`departement`	No	Filter to a French département (e.g. "75" Paris, "13" Bouches-du-Rhône)
`only_active`	No	Restrict to currently active units (default true)
`postal_code`	No	Filter to a 5-digit French postal code
`employee_range`	No	Employee count band: NN \| 00 \| 01 \| 02 \| 03 \| 11 \| 12 \| 21 \| 22 \| 31 \| 32 \| 41 \| 42 \| 51 \| 52 \| 53 (Sirene tranche codes)

Output Schema

TableJSON Schema

Name	Required	Description
`page`	No	Current page number
`results`	No	Array of matching legal units
`per_page`	No	Results per page
`total_results`	No	Total number of matching results

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 18, 2026
- changedOutput schema / properties / results / items / properties / sigle / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```

Changed2 schema fields changedMay 24, 2026

addedInput schema / examples

Added value: +[
+  {
+    "query": "Acme SARL Paris"
+  },
+  {
+    "ape": "6201Z",
+    "departement": "75",
+    "per_page": 20,
+    "query": "Sophie Martin directrice"
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "page": {
+      "description": "Current page number",
+      "type": "number"
+    },
+    "per_page": {
+      "description": "Results per page",
+      "type": "number"
+    },
+    "results": {
+      "description": "Array of matching legal units",
+      "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": "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",
+      "type": "number"
+    }
+  },
+  "type": "object"
+}

First observedMay 13, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so safety is well covered. The description adds useful behavioral detail: it is a full-text search and it returns specific fields like SIREN, establishments, and sector code. No contradiction with annotations was found.

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?

Two concise sentences, front-loaded with the core purpose and followed by relevant match/return details. No filler or redundant restatement of the tool name.

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?

For a moderately complex search tool with full schema coverage, rich annotations, and an output schema, the description is sufficient to orient an agent. It lacks explicit sibling differentiation, but the French legal unit scope and field list make invocation and selection reasonably clear.

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?

Schema description coverage is 100%, so baseline is 3. The description adds a small but meaningful extra: query matches 'sigle' in addition to the schema-listed name/director/address, and it clarifies the overall return scope. This is modest added value beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states a specific verb and resource: 'Full-text search across French legal units' and lists matchable fields (name, sigle, director names, addresses). It is clear about what the tool does, though it does not explicitly distinguish itself from sibling tools like search_within or entity_profile.

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 context for when to use the tool: when searching French legal units by name, director, or address. It does not explicitly mention alternatives or exclusion criteria, but the context is strong enough to guide basic tool selection.

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

All Entreprises Fr 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.