Skip to main content
Glama

Rulepass e-invoicing

Find a company on Peppol

lookup_peppol_participant
Read-only

Looks up a Peppol participant in the public Peppol Directory: whether it is listed and accepts Peppol BIS invoices and credit notes. notListed is not proof it cannot receive invoices; ask the customer.

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": "lookup_peppol_participant"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesscheme:id, e.g. 0208:0123456749 (Belgian enterprise number) or 9944:NL123456789B01.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety and external-data profile is covered. The description adds real value beyond that by identifying the data source (public Peppol Directory) and warning that a notListed outcome is not conclusive proof of inability to receive invoices. Rate limits or auth requirements are not mentioned.

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?

Two short sentences with no waste: the capability comes first and the interpretive caveat second. Every clause carries information an agent needs.

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?

For a single-parameter read-only lookup with no output schema, the description covers what is queried, where the data comes from, and how to read a negative result. It does not sketch the shape of a positive response, which would be the remaining gap, though the intended information content is stated.

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%, and the schema already explains the scheme:id format with two concrete examples. The description adds nothing about the id parameter, 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?

States a specific verb ('looks up') and resource ('Peppol participant in the public Peppol Directory') and names what the result conveys: listing status plus whether it accepts Peppol BIS invoices and credit notes. That is clearly distinct from a VAT lookup or an invoice check.

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

Usage Guidelines3/5

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

Usage is implied by the purpose but never stated as when-to-use, and no alternative tool is named. The only guidance is an interpretive caveat about notListed results, which helps after the call rather than in choosing it.

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.