Skip to main content
Glama
cmendezs

mcp-facture-electronique-fr

search_directory_line

Search for electronic invoice receiving addresses of a company by SIREN, SIRET, or routing code. Returns paginated directory lines to verify recipient registration and identify their Approved Platform.

Instructions

Search directory lines (electronic invoice receiving addresses) for a taxable entity.

A directory line maps an addressing identifier (SIREN, SIREN/SIRET, or SIREN/SIRET/routing-code) to an Approved Platform and an optional technical address. It is the authoritative record of where the recipient wants to receive invoices.

BEHAVIOR:

  • Returns a paginated list of matching directory lines; empty list if the entity has no registered lines.

  • At least one search criterion should be provided; omitting all may return an error or a very large result set.

  • Pagination: if the response contains 'nextUpdatedAfter', pass it as updated_after to retrieve the next page.

  • A recipient can have several lines (e.g. one at SIREN level plus specific ones per SIRET or routing code); the most specific line (SIREN/SIRET/routing-code) takes precedence over less specific ones.

RESPONSE: each item includes instanceId, addressingIdentifier (SIREN[/SIRET[/routingCode]]), approvedPlatformId, technicalAddress (optional), and timestamps (createdAt, updatedAt). The instanceId is required for update_directory_line and delete_directory_line.

USAGE GUIDELINES:

  • Prefer get_directory_line with the full addressingIdentifier when you know the exact address (faster, avoids pagination).

  • Use search_directory_line with siren to audit all receiving addresses of a company.

  • Call before sending an invoice to verify the recipient has a registered line and identify their AP.

  • If no lines are returned, the recipient is not yet registered in the PPF directory and cannot receive electronic invoices; they must register via create_directory_line or through their AP.

  • The instanceId from results is needed to call update_directory_line or delete_directory_line.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sirenNoTaxable entity SIREN (9 digits). Returns all directory lines (at SIREN, SIRET, and routing-code level) registered for this company. Most common starting point.
siretNoSpecific establishment SIRET (14 digits). Narrows results to lines for this establishment only.
routing_codeNoFilter by routing code associated with the directory line. Use to find the exact line for a department-level address.
platform_idNoFilter by Approved Platform identifier. Use to list all lines managed by a specific AP.
updated_afterNoPagination cursor: only return lines 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.
limitNoMaximum number of results per page (1-500, default 50).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

With no annotations provided, the description fully covers behavior: pagination, empty result possibility, requirement for at least one criterion, precedence of lines, and response fields. 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.

Conciseness4/5

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

Well-structured with clear sections (BEHAVIOR, RESPONSE, USAGE GUIDELINES). While comprehensive, it is slightly lengthy but every sentence adds value. Front-loaded with core purpose.

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

Completeness5/5

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

Given the tool's complexity (6 params, no annotations, multiple siblings), the description is remarkably complete: covers behavior, response format, pagination, usage guidelines, and even connects to other tools (e.g., instanceId needed for updates).

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 useful context beyond schema, e.g., 'siren is the most common starting point' and pagination cursor explanation. Still, the schema already covers parameter meaning well.

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 it searches directory lines (electronic invoice receiving addresses). It explains what a directory line is and distinguishes from get_directory_line, which is for exact address lookup.

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

Usage Guidelines5/5

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

Includes a dedicated 'USAGE GUIDELINES' section with explicit when-to-use (e.g., audit all addresses), when-to-prefer alternative (get_directory_line), and what to do if no lines returned. Provides clear context for tool selection.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/cmendezs/mcp-facture-electronique-fr'

If you have feedback or need assistance with the MCP directory API, please join our Discord server