Skip to main content
Glama

supplier_due_diligence

Screen suppliers by company name with VAT, company registry, LEI and sanctions checks, returning a pass/review/fail verdict and risk flags.

Instructions

Supplier due diligence for any company name (optionally VAT number and country): VIES VAT check, UK Companies House profile when country=GB, GLEIF LEI candidates with entity and registration status, and sanctions screening (OFAC, EU, FR, UK), with a pass/review/fail verdict and flags. Costs 0.01 USDC on Base per successful call (x402). Without a payment key this tool returns the 402 challenge.

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

Input Schema

NameRequiredDescriptionDefault
vatNoEU VAT number (optional)
nameYesCompany name
countryNoISO alpha-2

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A4.4/5.0
Behavior4/5

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

No annotations exist, so the description carries the full burden; it discloses cost (0.01 USDC on Base, x402), billing per successful call, and the failure mode of returning a 402 challenge without a key. It omits what happens when a company matches nothing, whether sanctions matching is fuzzy, and any rate or latency characteristics.

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 sentences, front-loaded with the purpose and followed by the payment model. The enumeration of checks is dense but every item is meaningful to an agent deciding whether this tool covers its need; nothing is redundant.

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 multi-source composite tool with no annotations and no output schema, the description covers scope, cost, auth requirement, and the shape of the result (pass/review/fail verdict plus flags). It leaves open how to obtain a payment key and how missing source data is reflected in the verdict, which is a minor but real gap.

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 baseline is 3, but the description adds genuine meaning the schema lacks: country=GB conditionally triggers the UK Companies House profile, and vat is specified as an EU VAT number feeding the VIES check. This ties parameters to concrete downstream behavior rather than restating types.

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 capability: supplier due diligence on a company name, then enumerates the constituent checks (VIES VAT, UK Companies House, GLEIF LEI, OFAC/EU/FR/UK sanctions) and the verdict output. This clearly separates it from narrower siblings like eu_vat, kyb_check_uk, or lei_lookup, which each cover one source.

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?

Gives clear input framing ('for any company name, optionally VAT number and country') and the operational precondition for payment (needs a payment key or gets a 402). It does not explicitly state when to prefer this composite over the single-source siblings, so no exclusion guidance is present.

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