Skip to main content
Glama

Sanctions Screening (OFAC/EU/UN)

Screen a name against all lists

screen_name

Free tier: limited to a small daily quota per client. Screens one person or entity name against the combined OFAC SDN, EU Consolidated and UN Consolidated lists using a 4-tier match pipeline (exact / alias / fuzzy / fuzzy-alias). Returns ranked candidates with match_type, confidence and scoring breakdown. Price beyond the free quota: $0.002 per call, paid via x402 in USDC on Base.

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_name": "<query_name>"
    },
    "name": "screen_name"
  }
}

Input Schema

NameRequiredDescriptionDefault
thresholdNoOptional fuzzy match threshold, 0.0-1.0. Defaults to 0.8.
query_nameYesPerson or entity name to screen
entity_typeNoOptional. Defaults to individual.

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?

With no annotations, the description carries the full burden and does so well: it discloses a per-client daily quota, the $0.002 per-call price after quota, the payment rail (x402 in USDC on Base), and the ranking/scoring output shape. It does not say whether calls are idempotent or what an empty/error result looks like, which keeps it short of full marks.

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?

Four tight sentences with no filler and a useful return-shape clause. Slight deduction because it leads with free-tier quota and price rather than the core action, pushing the most important information to the second sentence.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only screening tool with three well-documented parameters and no output schema, the definition is complete: it names the lists screened, the matching pipeline, the returned fields, and the commercial/quota constraints. An agent has everything needed to decide to call it and interpret the result.

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%, so threshold (0.0-1.0, default 0.8), query_name and entity_type are already fully documented. The description adds the pipeline context that explains why a threshold exists, but gives no extra detail on entity_type semantics or how threshold interacts with the alias/fuzzy tiers.

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 ('Screens one person or entity name') plus the exact data sources (OFAC SDN, EU Consolidated, UN Consolidated) and the matching approach (4-tier exact/alias/fuzzy/fuzzy-alias). The phrase 'one person or entity name' implicitly separates it from the batch sibling, so an agent can pick correctly without opening another schema.

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 context is implied rather than stated: 'one ... name' suggests this is the single-record call versus screen_batch, and the free-tier/pricing note tells the agent when cost applies. There is no explicit when-to-use/when-not, and no mention of screen_ownership_50pct or when ownership screening is the better choice.

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.