Skip to main content
Glama
cmendezs

mcp-facture-electronique-fr

search_directory_line

Search for registered electronic invoice receiving addresses of a French taxable entity by SIREN, SIRET, or other criteria. Use to verify recipient registration and identify their approved platform before sending invoices.

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 carries full burden and does an excellent job. It describes pagination behavior with nextUpdatedAfter, the requirement for at least one search criterion (otherwise possible error), and precedence of most specific lines. 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?

The description is well-structured with sections (BEHAVIOR, RESPONSE, USAGE GUIDELINES) and front-loaded with the core purpose. Every sentence adds value, and the length is justified by the complexity of the tool.

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 (pagination, multiple addressing levels, relationship with other tools), the description is fully comprehensive. It explains the response structure, the instanceId's role for other tools, and the business context. Output schema exists but description summarizes it well.

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 coverage is 100% with good parameter descriptions. The description adds value by explaining the pagination flow, the purpose of using siren vs other filters, and why omitting criteria may error. This goes beyond the schema details, so a 4 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 tool searches directory lines (electronic invoice receiving addresses) for a taxable entity, and distinguishes it from get_directory_line by explaining the difference between search vs exact lookup. It also explains what a directory line is, which adds context.

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?

The explicit 'USAGE GUIDELINES' section provides clear when-to-use and when-not-to-use guidance. It recommends get_directory_line for known exact addresses, search_directory_line for auditing, and specifies pre-invoice verification. It also explains what to do if no lines are returned.

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