Skip to main content
Glama

screen_sanctions

Read-onlyIdempotent

Free screening of a name or entity against official sanctions lists, each fetched from the authority that issues it: the OFAC SDN list from the US Treasury (SDN.CSV plus ALT.CSV for alternate spellings), the EU consolidated financial sanctions list from the European Commission, and the UK Sanctions List from the FCDO. THE UN CONSOLIDATED LIST IS NOT SCREENED -- it carries no licence permitting commercial redistribution, so we do not claim it. ALWAYS check lists_screened on the response: it names the lists that actually ran ON THAT CALL, and a list that failed to load appears in sources_unavailable instead. reason_code is 'partial_screening' whenever any source was unavailable, never 'clear'. Returns screening_status ('hit' | 'clean' | 'candidates' | 'not_screened' -- branch on THIS, not on matched, because matched:false is also false when nothing could be screened), matched: bool, a list of matches with score, program, and source URL, and which lists were screened. Never fabricates a match or a clear -- if no match is found, explicitly names which lists were checked.

EXAMPLE USER QUERIES THAT MATCH THIS TOOL: user: "Screen this vendor before we pay them: ACME Trading LLC, Russia" -> call screen_sanctions({"name": "ACME Trading LLC", "country": "RU", "type": "entity"}) user: "Is Kim Jong-un on the OFAC list?" -> call screen_sanctions({"name": "Kim Jong-un", "country": "KP", "type": "person"}) user: "Run a sanctions check on this person before onboarding" -> call screen_sanctions({"name": "Ivan Petrov", "country": "RU", "type": "person"}) user: "Do a compliance check -- is this company sanctioned?" -> call screen_sanctions({"name": "Mahan Air", "country": "IR", "type": "entity"})

WHEN TO USE: Use before onboarding a counterparty, processing a payment, engaging a vendor, or doing any due-diligence step that requires knowing whether a person or entity appears on official sanctions lists. Essential for agents doing business formation, vendor qualification, payments onboarding, trade compliance, or any workflow where a sanctioned counterparty is a legal or reputational risk. WHEN NOT TO USE: Do not use as a substitute for full KYC/AML screening -- this covers sanctions lists only, not PEP (Politically Exposed Person) databases, adverse media, or credit risk. Do not treat a negative result as a compliance clearance; it is informational only. Do not use for bulk screening of large lists -- each call is a live API query. COST: free within the daily quota, then $0.02 per call LATENCY: ~2000ms

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesFull name of the person or entity to screen, e.g. 'Kim Jong-un' or 'ACME Trading LLC'. Use the most complete name available for best accuracy.
typeNoOptional entity type hint. 'person' for individuals, 'entity' for organizations/companies. Omit to screen both.
countryNoOptional ISO 3166-1 alpha-2 country code or country name (e.g. 'IR', 'Iran'). It ANNOTATES AND RANKS results; it never removes any. Each EU/UK match carries country_match: true, false, or null when the listing records no country. Nothing is dropped on a mismatch, because the country we hold is the address/nationality on the listing rather than everywhere a party operates - excluding on it would return a clean screen for someone who IS listed.

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already mark the tool read-only, idempotent, and non-destructive. The description adds critical runtime behavior: lists are fetched from issuing authorities, UN list is intentionally skipped for licensing reasons, partial-screening failure appears via lists_screened/sources_unavailable/reason_code, and screening_status should be trusted over matched. An agent can correctly interpret ambiguous results because of this detail.

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?

The description is long but well-organized under clear headings and every block earns its place: source provenance, failure semantics, response-field guidance, usage triggers, cost, and latency. The critical caveats are front-loaded near the beginning and the examples support parameter mapping.

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?

Even without an output schema, the description fully specifies the response contract: screening_status enum with branch-on-this instruction, matched boolean, match details, lists_screened, sources_unavailable, and reason_code. It also covers cost, latency, and when not to use the tool, so an agent has what it needs to call and interpret the tool correctly.

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?

The schema already documents all three parameters with 100% coverage, including the country parameter's annotate-and-rank semantics. The description's example queries add illustrative mappings from user requests to parameter values, but they do not add materially new parameter meaning beyond what the schema provides.

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?

The opening sentence states a specific action — screening a name or entity against official sanctions lists — and enumerates the exact lists screened (OFAC SDN, EU consolidated, UK FCDO) and the UN list excluded. This clearly distinguishes the tool from compliance-adjacent siblings like check_compliance and map_trade_restriction.

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?

Dedicated WHEN TO USE and WHEN NOT TO USE sections give concrete triggers: onboarding, payments, vendor engagement, due diligence. They also explicitly exclude KYC/AML/PEP/adverse-media screening and bulk screening. It does not name a specific sibling tool as the alternative, but the exclusions are clear.

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.

TDQS

A4.5/5.0
Disambiguation5/5

Each tool has a clear, distinct purpose with detailed descriptions and explicit WHEN TO USE / WHEN NOT TO USE guidance. Potential overlaps like send_message vs. send_transactional_confirmation are well-differentiated by idempotency and use case, and compliance tools (check_compliance, screen_sanctions, map_trade_restriction) operate on different scopes without ambiguity.

Naming Consistency5/5

All tool names use lowercase snake_case and follow a consistent verb_noun pattern (call_business, check_quota, find_business, send_message, verify_company_record). Even less standard verbs like lookup, map, and mint follow the same structural convention, and there are no mixed casing styles or inconsistent naming patterns.

Tool Count4/5

With 23 tools, this is slightly above the typical 3-15 range, but the breadth of the server's purpose—covering communication, scheduling, compliance, trade screening, and operational utilities—justifies the count. Each tool addresses a distinct capability area, and the set is not bloated with redundant or trivial functions.

Completeness5/5

The tool surface covers the full lifecycle of the broker's domain: business discovery, booking (check, import, schedule), communication (send, receive, read), compliance (pre-flight checks, sanctions, trade restrictions, company verification), and operational support (quota, health, cost preview, key minting, async status/outcome). There are no obvious dead ends or missing critical operations for the stated purpose.