mcp-facture-electronique-fr

Overview Schema Source Related Servers Discussions Admin

search_establishment

Search for French establishments (SIRETs) in the PPF Annuaire using SIRET, SIREN, or partial name, with pagination and filtering options.

Instructions

Search establishments (SIRETs) in the PPF Annuaire (POST /siret/recherche).

Input Schema

TableJSON Schema

Name	Required	Description
`siren`	No	Parent SIREN (9 digits). Lists all establishments.
`siret`	No	Exact SIRET (14 digits, no spaces).
`limite`	No	Maximum number of results (limite).
`ignorer`	No	Number of results to skip for pagination (ignorer).
`denomination`	No	Establishment name (partial match).
`etat_administratif`	No	Administrative status filter (etatAdministratif).

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed9 schema fields changedv0.7.0Jul 5, 2026

removedInput schema / properties / administrative_status

Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "description": "Administrative status of the establishment in the PPF directory. Active: establishment is open and reachable for invoicing. Inactive: establishment is closed; invoices cannot be sent to it."
-}

addedInput schema / properties / denomination

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Establishment name (partial match)."
+}

addedInput schema / properties / etat_administratif

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Administrative status filter (etatAdministratif)."
+}

addedInput schema / properties / ignorer

Added value: +{
+  "default": 0,
+  "description": "Number of results to skip for pagination (ignorer).",
+  "minimum": 0,
+  "type": "integer"
+}

removedInput schema / properties / limit

Removed value: -{
-  "default": 50,
-  "description": "Maximum number of results per page (1-500, default 50).",
-  "maximum": 500,
-  "minimum": 1,
-  "type": "integer"
-}

addedInput schema / properties / limite

Added value: +{
+  "default": 50,
+  "description": "Maximum number of results (limite).",
+  "maximum": 500,
+  "minimum": 1,
+  "type": "integer"
+}

changedInput schema / properties / siren / description

Previous value: -"Parent company SIREN (9 digits). Returns all establishments registered under this company. Use to discover all SIRETs for a given SIREN."New value: +"Parent SIREN (9 digits). Lists all establishments."

changedInput schema / properties / siret / description

Previous value: -"Establishment SIRET number (14 digits, no spaces). Example: '12345678900012'. Use when you know the exact establishment; returns at most one result."New value: +"Exact SIRET (14 digits, no spaces)."

removedInput schema / properties / updated_after

Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "description": "Pagination cursor: only return establishments updated after this date/time (ISO 8601, e.g. 2024-09-01T00:00:00Z). Use the 'nextUpdatedAfter' field from the previous response to fetch the next page."
-}

Changed5 schema fields changedv0.2.2Apr 29, 2026

changedInput schema / properties / administrative_status / description

Previous value: -"Administrative status of the establishment. Values: Active (open), Inactive (closed)."New value: +"Administrative status of the establishment in the PPF directory. Active: establishment is open and reachable for invoicing. Inactive: establishment is closed; invoices cannot be sent to it."

changedInput schema / properties / limit / description

Previous value: -"Maximum number of results (1-500)."New value: +"Maximum number of results per page (1-500, default 50)."

changedInput schema / properties / siren / description

Previous value: -"Parent company SIREN (9 digits). Returns all establishments of this company."New value: +"Parent company SIREN (9 digits). Returns all establishments registered under this company. Use to discover all SIRETs for a given SIREN."

changedInput schema / properties / siret / description

Previous value: -"Establishment SIRET number (14 digits, no spaces). Example: '12345678900012'."New value: +"Establishment SIRET number (14 digits, no spaces). Example: '12345678900012'. Use when you know the exact establishment; returns at most one result."

changedInput schema / properties / updated_after / description

Previous value: -"ISO 8601 pagination (e.g. 2024-09-01T00:00:00Z)."New value: +"Pagination cursor: only return establishments updated after this date/time (ISO 8601, e.g. 2024-09-01T00:00:00Z). Use the 'nextUpdatedAfter' field from the previous response to fetch the next page."

First observedv0.2.0Apr 28, 2026

TDQS

B3.1/5.0

Behavior2/5

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

No annotations are provided, so the description carries full burden. It mentions the HTTP method and endpoint but does not disclose behavioral traits such as pagination details, rate limits, what happens on empty results, or any side effects. The description repeats the endpoint name but adds little behavioral insight.

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?

Extremely concise at one sentence. No redundancy. However, it sacrifices necessary context for brevity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 6 parameters and no annotations, the description is too brief. It does not explain the purpose of common filters (e.g., siren vs siret), pagination, or the output schema (though output schema exists). Lacks completeness for a search tool.

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 already documents all parameters. The description adds no additional meaning beyond what is in the schema. 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 clearly states the action ('Search establishments (SIRETs)') and the resource ('PPF Annuaire') with a specific endpoint ('POST /siret/recherche'). It distinguishes from sibling tools like 'search_company' which search for companies, not establishments.

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?

The description provides no guidance on when to use this tool versus alternatives (e.g., 'search_company'), no prerequisites, and no scenarios where another tool would be preferred. It simply states the endpoint.

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