Skip to main content
Glama

EU e-invoicing and business checks (EN 16931, Peppol, VAT, sanctions)

Can this company receive e-invoices? (Peppol + mandate)

einvoice_route
Read-onlyIdempotent

'Can I e-invoice this company?' id = EU VAT number (e.g. 'BE0403170701') or Peppol id ('0208:0403170701'). Returns VIES VAT status, Peppol registration (Peppol Directory, then SML/SMP; BIS 3 invoice support), the country's B2B e-invoice mandate (dates, format, source) and the recommended format for create_einvoice. France's PPF directory is not included yet.

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": {
      "id": "<id>"
    },
    "name": "einvoice_route"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesBuyer's EU VAT number (e.g. 'BE0403170701') or Peppol participant id (e.g. '0208:0403170701').

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / id / description
      Added value: +"Buyer's EU VAT number (e.g. 'BE0403170701') or Peppol participant id (e.g. '0208:0403170701')."
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety bar is low; the description adds genuine value by naming the data sources and fallback chain (VIES, Peppol Directory, then SML/SMP, BIS 3 support). It also discloses a real coverage limitation ('France's PPF directory is not included yet'), which is exactly the kind of caveat an agent needs before trusting a negative result.

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 framing question and result list are front-loaded and compact, with the format examples placed where they are needed. A little space is wasted repeating the id formats already in the schema.

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?

There is no output schema, so the description must carry the return-value burden, and it does enumerate the returned components at a useful level of detail. It would be stronger if it said what a negative or partially resolvable result looks like, given the multi-source lookup.

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% and the single 'id' parameter already documents the accepted EU VAT number and Peppol id formats with examples. The description restates the same formats rather than adding new meaning, so the baseline of 3 applies.

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 opens with the exact decision the tool answers ('Can I e-invoice this company?') and enumerates the concrete outputs: VIES VAT status, Peppol registration, B2B mandate with dates/format/source, and a recommended format. It also names the sibling it feeds into (create_einvoice), so an agent can tell this routing lookup apart from verify_vat or lookup_company.

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?

Usage context is clear: call it to decide whether a counterparty can receive an e-invoice and which format to use, with an explicit handoff to create_einvoice for the recommended format. It does not state exclusions or say when to prefer verify_vat/verify_eori instead, so it stops short of a full when/when-not statement.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.