Skip to main content
Glama

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

Counterparty due-diligence report

due_diligence_report
Read-onlyIdempotent

Counterparty due-diligence report in one call: VIES VAT, official business register, EU/UN/OFAC/UK sanctions, EC EORI, GLEIF LEI and Peppol e-invoice route, with deterministic risk flags, 0-100 risk score, pass/review/fail verdict, sources and UTC timestamp. company: VAT ID (best), registry number or name; country: ISO code for names.

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": {
      "company": "<company>"
    },
    "name": "due_diligence_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
companyYesCompany VAT number (best) or company name.
countryNoOptional ISO two-letter country code when a name is given.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / company / description
      Added value: +"Company VAT number (best) or company name."
    • addedInput schema / properties / country / description
      Added value: +"Optional ISO two-letter country code when a name is given."
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover readOnly, openWorld, idempotent and non-destructive, but the description goes further by naming the concrete external sources queried and describing the return shape: deterministic risk flags, a 0-100 score, a pass/review/fail verdict, sources and a UTC timestamp. It does not say what happens on no-match or partial-source failure, which would have pushed this higher.

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 core capability is front-loaded in a single dense sentence, followed by a compact parameter hint. The enumerated source list is long but every item earns its place by signalling coverage; minor cost is that it reads as a run-on list.

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 correctly carries the burden of describing return values (flags, score, verdict, sources, timestamp), and both parameters are explained. Gaps are minor: no guidance on behavior when a source returns nothing or when the company cannot be resolved.

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%, so both parameters are already documented in the schema. The description adds one small piece of meaning not in the schema — that a registry number is also accepted alongside VAT ID or name — and repeats the 'VAT ID (best)' preference already stated in the schema, so the net addition is marginal.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource ('Counterparty due-diligence report in one call') and enumerates exactly which checks it aggregates (VIES VAT, business register, EU/UN/OFAC/UK sanctions, EORI, GLEIF LEI, Peppol route). This clearly separates it from single-purpose siblings like verify_vat or screen_sanctions, though it never names those siblings explicitly.

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?

The phrase 'in one call' plus the full list of checks implies this is the aggregate tool to use instead of chaining individual verifications, but that is left to inference. There is no explicit statement of when to prefer it over kyb_check or the individual verify_* tools, and no exclusions or prerequisites.

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.