Skip to main content
Glama

sanctions_check

Screen individuals, companies, or vessels against US, EU, French, and UK sanctions lists using fuzzy matching to get match scores and programme details.

Instructions

Sanctions screening of a person, company or vessel name against the US Consolidated Screening List (OFAC SDN with aliases plus other Treasury, Commerce BIS and State lists), the EU consolidated financial sanctions list (FSF), the French national asset-freeze register (DG Trésor) and the UK sanctions list (FCDO). Fuzzy Jaro-Winkler token matching with score, programmes, DOB; lists refreshed daily. Costs 0.005 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": "sanctions_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
maxNo1-50
nameYesName to screen
typeNoperson, entity or vessel (optional)
listsNoofac,eu,fr,uk (default all)
thresholdNo0.7-1, default 0.88

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the matching method (fuzzy Jaro-Winkler), what fields come back (score, programmes, DOB), list refresh cadence, the per-call price and the x402 402-challenge behavior. It stops short of stating rate limits or how low-confidence matches are surfaced, but the operational picture is unusually complete.

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?

Purpose is front-loaded in the first clause, followed by sources, mechanics, and commercial/operational terms in logical order. The single long opening sentence with nested parentheses is dense but 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 5-parameter screening tool with no output schema, the definition covers inputs, matching method, returned fields, data freshness, pricing and the payment-failure path. Only rate/throughput behavior and confidence-interpretation guidance are absent.

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 adds meaning by naming the four list sources that map to the 'lists' values and explaining that matching is scored, which gives context to 'threshold' and 'max'. It does not spell out the threshold scale or 'type' options beyond the schema's own text.

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+resource ('Sanctions screening of a person, company or vessel name') and enumerates the exact lists screened (OFAC SDN, EU FSF, DG Trésor, UK FCDO), which clearly separates it from the KYB and company-registry siblings.

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 description implies its scope (name screening only, not company registration or KYB) but never explicitly routes the agent between this and siblings like kyb_check_eu or fr_company, nor states when-not to use it. The payment note ('without a payment key this tool returns the 402 challenge') does give a concrete precondition for invoking it.

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