Skip to main content
Glama
cmendezs

mcp-facture-electronique-fr

by cmendezs
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

search_routing_code

Find routing codes in the PPF directory using SIRET, SIREN, or exact code to route invoices to the correct internal unit.

Instructions

Search routing codes registered in the PPF directory for a recipient.

Routing codes subdivide a SIRET receiving address to department or service level, allowing a company to route invoices to different internal units (e.g. purchasing, accounting).

BEHAVIOR:

  • Returns a paginated list of matching routing codes; empty list if none defined for the criteria.

  • At least one of siret, siren, or routing_code should be provided.

  • A SIRET may have zero or more routing codes; zero means invoices go to the SIRET-level address.

RESPONSE: each item includes instanceId, siret, siren, routingCode, label (optional), and timestamps. The instanceId is required to update or delete a routing code.

USAGE GUIDELINES:

  • Call before create_directory_line with a routing_code to confirm the code exists on the target SIRET.

  • Call to enumerate available routing codes when helping a sender choose the correct recipient address.

  • If no routing codes exist for a SIRET, the invoice must be addressed at SIRET level without a routing code.

  • Use create_routing_code to create a new code; use update_routing_code with instanceId to rename it.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
siretNoEstablishment SIRET (14 digits). Returns all routing codes associated with this establishment. Most common filter: use when building a directory line for a specific SIRET.
sirenNoCompany SIREN (9 digits). Returns routing codes for all establishments under this company.
routing_codeNoExact routing code value to look up (e.g. 'ACCOUNTS-DEPT', 'REGION-WEST'). Use to verify a routing code exists before referencing it in an invoice.
limitNoMaximum number of results per page (1-500, default 50).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Tool Definition Quality

A4.2/5.0
Behavior4/5

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

No annotations provided; description bears full burden. BEHAVIOR section notes pagination, empty results, requirement for at least one filter, and that SIRET may have zero or more routing codes. Covers key behaviors well, though could explicitly state it is read-only.

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). Somewhat lengthy but each section adds value. Could be slightly more concise, but organization aids readability.

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 complexity (4 parameters, pagination, multiple filters) and absence of annotations, the description is comprehensive. It explains purpose, behavior, response fields, usage context, and ties into sibling tools. Output schema exists, so return values are covered. No gaps.

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 baseline is 3. Description adds the note that at least one of siret, siren, or routing_code should be provided, which is not in schema. Otherwise, parameter details are already in schema. No significant additional semantics.

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?

Description states the tool searches routing codes for a recipient. It explains the concept of routing codes subdividing a SIRET. Purpose is clear and specific, but does not explicitly differentiate from sibling search tools like search_directory_line.

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?

Has a dedicated USAGE GUIDELINES section that lists when to call (before create_directory_line with routing_code, to enumerate codes), when not to use (no routing codes means invoice at SIRET level), and alternatives (use create_routing_code, update_routing_code). Excellent guidance.

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