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. Dates show when Glama detected each change.

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

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, destructiveHint=false. The description adds return fields and matching behavior, which is useful but not critical beyond annotations. No contradictions.

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 sentences, 30 words for the first sentence. Zero waste, all information is relevant and directly stated. Front-loaded with the core purpose.

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 complexity (8 parameters, output schema exists, annotations present), the description adequately covers scope, matching, and return fields. Could mention query requirement, but overall complete.

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 schema fully documents all 8 parameters. The tool description adds no additional meaning beyond summarizing return fields and matching scope. Baseline 3 is appropriate.

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 uses a specific verb ('search') and resource ('French legal units'), details matching fields (name, sigle, director names, addresses) and return fields (SIREN, denomination, etc.), clearly distinguishing it from siblings like 'search_within' or 'nearby'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives like 'search_within', 'nearby', or 'entity_profile'. The description only states what it does, not when it's preferred or when not to use it.

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

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.