Skip to main content
Glama

Search the Peppol Directory (free)

search_peppol_directory
Read-onlyIdempotent

Free, no sign-in needed: search the official Peppol Directory (directory.peppol.eu) by company name, Belgian enterprise/VAT number or Peppol ID such as 0208:0403170701, optionally in one country. Returns matching participants grouped per company: their Peppol IDs (scheme and ID), country, registration date and whether they list Peppol BIS Billing 3.0 invoices and credit notes; Belgian companies show whether 0208, 9925 or both are listed. Listing in the Directory is optional, so a missing company may still receive Peppol invoices — confirm a Belgian number live with check_peppol_receivability. Shares the 20 free calls per hour per connection with check_peppol_receivability.

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": {
      "query": "<query>"
    },
    "name": "search_peppol_directory"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoResult page of a name search (20 per page), 0 to 4.
queryYesCompany name (at least 3 letters), Belgian enterprise or VAT number (BE0403170701), or Peppol ID (0208:0403170701).
countryNoISO country code to limit a name search, e.g. 'BE'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, openWorld, idempotent); the description adds real operational context beyond them: a shared 20-calls-per-hour rate limit with a named sibling and the optional-listing caveat that affects how results should be interpreted. It also describes what is returned per company (scheme/ID, country, registration date, BIS Billing 3.0 invoice/credit-note flags, Belgian 0208/9925 schemes), so little behavioral information is missing.

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?

Front-loaded with the free/no-sign-in fact and the searchable keys, with the caveat and rate limit placed at the end where they belong. Dense and slightly run-on across a semicolon and em dash, but no sentence is filler.

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?

With no output schema, the description carries the return-value explanation and does so adequately, and it covers cost, rate limits, and alternatives. The only omission is the pagination parameter's behavior (20 per page, pages 0-4), which the schema covers but the description does not.

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, but the description meaningfully clarifies the 'query' parameter beyond the schema by stating it needs at least 3 letters for a name search (the schema only sets minLength 1) and by giving concrete ID/VAT formats. The 'page' parameter is not addressed in the description, which keeps this from a 5.

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 ('search the official Peppol Directory') plus the exact accepted query forms (company name, Belgian enterprise/VAT number, Peppol ID like 0208:0403170701) and the endpoint directory.peppol.eu, which separates it from sibling lookup tools.

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?

Explicitly notes it is free and needs no sign-in, and routes the agent to check_peppol_receivability for live confirmation of a Belgian number. It also gives a 'when-not-to-trust-the-result' condition: Directory listing is optional, so a missing company may still receive Peppol invoices.

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.

Resources