Skip to main content
Glama

Sanctions Screening (OFAC/EU/UN)

Screen up to 100 names in one priced call

screen_batch

Paid: $0.02 per call (up to 100 names), paid via x402 in USDC on Base. No free quota. Use this for onboarding batches rather than looping screen_name. Returns one result object per name, aggregated hit counts, and a screening id for your audit trail.

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_names": "<query_names>"
    },
    "name": "screen_batch"
  }
}

Input Schema

NameRequiredDescriptionDefault
thresholdNo
query_namesYesNames to screen, up to 100 per call

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does well: it discloses cost ($0.02 per call), the payment rail (x402, USDC on Base), the absence of a free quota, and what comes back (one result object per name, aggregated hit counts, a screening id for audit). What is missing is failure behavior — what happens on payment rejection, partial batches, or invalid names — which matters for a paid mutation-style call.

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?

Three tight sentences ordered by cost, then usage routing, then return shape — all front-loaded and free of filler. The 'up to 100 names' figure is repeated from the title and schema, a minor redundancy rather than a real cost.

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 two-parameter tool with no output schema and no annotations, the description covers the two things an agent most needs that structured fields cannot supply: that it is paid and how, and what the response contains. The unexplained threshold parameter is the one substantive hole in an otherwise complete definition.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 50%, and the uncovered parameter is threshold (0–1), which the description never mentions at all — an agent cannot tell whether it is a match-confidence cutoff or something else. The description's only parameter-adjacent content restates the 100-name cap already present in the title and the schema's maxItems, so it adds essentially no meaning beyond the schema.

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?

The description makes clear this is a batch screening call that takes up to 100 names in one priced request and returns per-name results. It distinguishes itself from the sibling screen_name by naming it as the looping alternative. What it screens against (sanctions/watchlists) is only implied by sibling context, not stated, which keeps it from a 5.

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?

It gives an explicit usage rule: use this for onboarding batches rather than looping screen_name, and warns that there is no free quota. That is clear when-to-use guidance plus a named alternative. It stops short of stating the inverse case (single-name lookups should go to screen_name) or any exclusion conditions.

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.