Skip to main content
Glama

Screen names against sanctions lists

screen_names
Read-onlyIdempotent

Use this when the user wants ofac search, sanctions screening, or batch ofac screening of 1 to 200 names with optional references, a type filter and a threshold from 70 to 100, plus a dated XLSX log. Matches use Latin transliterations and token similarity on SDN and Consolidated lists. Do not use for a legal determination, other government lists or ownership analysis.

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

Input Schema

NameRequiredDescriptionDefault
namesYesNames to screen, 1 to 200; each name has 1 to 200 characters and may have one TAB plus a reference of at most 60 characters. Example: ["Banco Nacional de Cuba", "Acme Widgets LLC\tVendor 7"].
thresholdNoWhole-number similarity threshold from 70 to 100, default 85. Example: 85.
entry_typeNoType filter: any (default), individual, entity, vessel, aircraft. Example: entity.

Output Schema

NameRequiredDescriptionDefault
listsYes
notesYes
errorsYes
summaryYes
warningsYes
downloadsYes
noMatchRowsYes
potentialMatchesYes

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?

Annotations already cover read-only, idempotent, open-world, and non-destructive behavior, but the description adds useful context beyond them: the matching method uses Latin transliterations and token similarity on SDN and Consolidated lists, and the output includes a dated XLSX log. It does not discuss authentication, rate limits, or failure behavior, but the added matching and output details are meaningful.

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 description is front-loaded with usage guidance and contains no filler; every sentence adds purpose, exclusions, or matching behavior. The first sentence is somewhat dense and run-on, but overall it is appropriately sized for the tool.

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?

Given the rich annotations, full schema coverage, and an output schema, the description supplies enough context for correct invocation: when to use it, when not to use it, how matching works, and that a dated XLSX log is produced. Nothing essential for an agent to call the tool correctly is missing.

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 all three parameters are already documented in the schema. The description restates batch size, optional references, type filter, and threshold range, but adds little syntax or meaning beyond what the schema provides, making the baseline 3 appropriate.

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 states a specific verb and resource: batch sanctions screening of 1 to 200 names against SDN and Consolidated lists, with matching via Latin transliterations and token similarity. It is clearly distinguishable from a single-entry lookup by emphasizing batch screening, though it does not explicitly name the sibling tool get_sanctions_entry.

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 explicit when-to-use guidance for OFAC search, sanctions screening, and batch screening, and explicit when-not-to-use exclusions for legal determinations, other government lists, and ownership analysis. It does not name a specific alternative tool for those excluded cases, which keeps it short of a 5.

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.

Resources