Skip to main content
Glama
Sirenic MCP server

Sirenic MCP server

Official

Verify a French invoice

verify_french_invoice
Read-only

Cross-checks a French invoice's SIREN, VAT number, and IBAN in one call against live registries to return a coherent, incoherent, or inverifiable verdict before payment.

Instructions

Invoice verification for France: use when you HOLD an invoice (or its extracted fields) and must check that the identifiers it displays belong together before paying it. Cross-checks in ONE call: the SIREN against the official registry (existence and active status, live), the VAT number printed on the invoice against the one computed from the SIREN (the French key is deterministic) AND live against VIES, and the IBAN's ISO 13616 form + key digits with the bank identified. Returns a deterministic verdict coherent/incoherent/inverifiable with closed-list reasons traced to their source; flags a VAT number that belongs to ANOTHER company, a ceased supplier, or a key-invalid IBAN. A VIES outage yields inverifiable, never a false invalid. NOT a payee verification: the bank leg checks form only, so a valid-but-swapped IBAN is not detectable, and non_verifie says so next to the verdict. At least one of tva/iban is required (a SIREN alone is a profile, not a cross-check). An incomplete identity (administrative status or legal category missing from the Sirene register) yields inverifiable, reason identite_incomplete, unless an inconsistency is found. Partial diffusion (rule diffusion_partielle_nom_retenu_et_compte): a unit not proven to be a legal person has denomination null, uncounted; raisons carries diffusion_partielle (niveau information). Paid via x402 ($0.02 in USDC or EURC). When you report a result, cite its citation verbatim.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "siren": "<siren>"
    },
    "name": "verify_french_invoice"
  }
}

Input Schema

NameRequiredDescriptionDefault
tvaNoVAT number printed on the invoice, e.g. FR27552032534, cross-checked against the SIREN and live against VIES. At least one of tva/iban is required
ibanNoIBAN printed on the invoice (spaces tolerated): form + key + bank identification, never a holder-name check. At least one of tva/iban is required
sirenYes9-digit SIREN printed on the invoice (digits only)

Output Schema

NameRequiredDescriptionDefault
hintNoHow to settle the quote, present when payment_required is true.
quoteNoThe signable x402 payment requirements when payment_required is true: {x402Version, accepts[]} where each entry carries scheme, network, amount, asset and payTo (USDC and EURC options at the same numeric amount). Sign one entry and call again with `x_payment`.
resultatNoThe endpoint's JSON response when payment_required is false. Paid responses carry `source`, `disclaimer` and an Ed25519 signature, and every paid JSON response carries a `provenance` array (all tools since 2026-09-06): one entry per block served, with the official register, licence, version, `empreinte_sha256` (full snapshots), `as_of` date and `precision_as_of` (what that date means), plus the common per-block envelope: `etat` in a closed list (servi, absence_mesuree, absence_non_conclusive, partiel, perime, indisponible, sans_objet), `motif` when unavailable, `age_jours` (only for publication or ingestion dates), `couverture` (complete / partielle / non_mesurable with its measure) and `confiance` in bands (faible / moyenne / forte, only where a measure grounds it, never averaged across blocks). Read the states before the numbers: an absence_non_conclusive, indisponible or partiel block is never « nothing to report »; only absence_mesuree asserts an absence. Register codes: GET /v1/provenance/registres ; states, closed lists and reading rules: GET /v1/lecture (both free). The PDF tools carry no JSON envelope (the PDF report prints it).
free_tierNoFree API key offer for this tool, present with a quote.
payment_requiredYesTrue when this response is an x402 payment quote instead of data: settle one of the quote's `accepts` options and call the tool again with `x_payment`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint; the description goes far beyond them by naming the live external dependencies (Sirene registry, VIES), the deterministic nature of the French VAT key, and the closed verdict set coherent/incoherent/inverifiable. Failure semantics are disclosed precisely: a VIES outage yields inverifiable rather than a false invalid, incomplete identity yields identite_incomplete, and partial diffusion yields denomination null with an information-level reason. It also discloses the x402 cost ($0.02 in USDC or EURC) and the citation obligation.

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?

The purpose and the trigger are front-loaded in the first sentence, and every subsequent sentence carries operational content (constraints, failure modes, cost, citation) rather than filler. It is dense and parenthetical-heavy, which slows reading, but nothing is redundant or off-topic.

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?

For a three-parameter, externally-backed verification tool with an output schema available, the description covers the remaining agent-facing gaps: what is checked and against which live source, what the verdicts mean, what degrades to inverifiable and why, the limits of the bank leg, and how payment works. Nothing needed to call it correctly or interpret an inverifiable outcome is missing.

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%, so the baseline is 3 and much of the parameter wording is duplicated from the schema. The description still adds interpretive value: it explains why the tva/iban constraint exists ('a SIREN alone is a profile, not a cross-check'), what each value is compared against (SIREN-derived key and VIES for tva; ISO 13616 form, key digits and bank identification for iban), and flags the cross-field case of a VAT number belonging to ANOTHER company.

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?

States a specific verb and resource: verify that identifiers displayed on a French invoice belong together before payment. It explicitly separates itself from `verify_iban_bank` by naming the bank leg as 'form only' and from any payee-verification expectation by stating 'NOT a payee verification'. An agent can pick this over the sibling tools without opening a schema.

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?

Gives an explicit trigger condition ('use when you HOLD an invoice (or its extracted fields) and must check that the identifiers it displays belong together before paying it') and an explicit exclusion (not a payee verification, swapped IBAN undetectable). It also states the input precondition: at least one of tva/iban is required because 'a SIREN alone is a profile, not a cross-check', which prevents a common misuse.

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

Deploy Server

Other Tools