Skip to main content
Glama
cmendezs

mcp-facture-electronique-fr

by cmendezs
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

get_establishment_by_siret

Look up establishment details, status, and approved platform from the PPF directory by SIRET number to verify the receiving address before sending an invoice.

Instructions

Look up an establishment in the PPF directory by its SIRET number. Essential for verifying the receiving address before sending an invoice. Returns the establishment details, its status, and its Approved Platform.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
siretYesEstablishment SIRET number (14 digits, no spaces). Example: '12345678900012'. Essential for verifying the receiving address before sending an invoice: confirms the establishment is registered and active in the PPF directory.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • tools/directory_tools.py:227-247 (handler)
    MCP tool handler function decorated with @mcp.tool() that calls the directory client's get_establishment_by_siret method. This is the actual entry point executed when the tool is invoked.
    @mcp.tool()
async def get_establishment_by_siret(
    siret: Annotated[
        str,
        Field(
            description=(
                "Establishment SIRET number (14 digits, no spaces). "
                "Example: '12345678900012'. "
                "Essential for verifying the receiving address before sending an invoice: "
                "confirms the establishment is registered and active in the PPF directory."
            )
        ),
    ],
) -> dict:
    """
    Look up an establishment in the PPF directory by its SIRET number.
    Essential for verifying the receiving address before sending an invoice.
    Returns the establishment details, its status, and its Approved Platform.
    """
    client = get_directory_client()
    return await client.get_establishment_by_siret(siret=siret)
  • tools/directory_tools.py:229-239 (schema)
    Input schema definition for the tool parameter: siret is a required string (14 digits) with a Pydantic Field description providing usage guidance.
    siret: Annotated[
    str,
    Field(
        description=(
            "Establishment SIRET number (14 digits, no spaces). "
            "Example: '12345678900012'. "
            "Essential for verifying the receiving address before sending an invoice: "
            "confirms the establishment is registered and active in the PPF directory."
        )
    ),
],

Tool Definition Quality

A4/5.0
Behavior3/5

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

No annotations provided, so description carries the burden. It discloses output includes 'establishment details, its status, and its Approved Platform,' but does not mention read-only nature, rate limits, or error cases. Adequate but not thorough.

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?

Very concise: two sentences that front-load purpose and key use case. Every sentence adds value.

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 presence of output schema (not shown but referenced), description sufficiently covers purpose and output. With a simple single-parameter tool, it is complete enough, though explicit sibling differentiation could improve.

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 coverage is 100% with parameter description already detailing the use case. The tool description adds minimal extra meaning (context about verifying address) but largely repeats schema content.

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?

Description uses specific verb ('Look up') and resource ('establishment in the PPF directory') and clearly distinguishes from siblings like search_establishment (exact vs search) and get_company_by_siren (different identifier).

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

Usage Guidelines4/5

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

Description states when to use: 'Essential for verifying the receiving address before sending an invoice.' It implies context but does not explicitly list when not to use or provide alternatives like search_establishment for non-exact lookups.

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