Skip to main content
Glama

Check names against the US Consolidated Screening List

screen_export_control
Read-only

Searches the US trade.gov Consolidated Screening List (Entity List, SDN, Denied Persons, Unverified, ITAR Debarred, etc.) by name and optional country. Each hit includes list name, aliases, addresses, programs, federal register notice, and match score. Related tools on this server, for a different need: screen_debarment when you need to check names against debarment and exclusion lists. Price: $0.003 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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": "screen_export_control"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesName or keyword to search (1–200 characters)
limitNoMax results to return (1–50, default 20)
countryNoOptional ISO-2 country code filter (e.g. RU, CN, IR)

Output Schema

NameRequiredDescriptionDefault
countNo
totalNo
sourceNo
resultsNo
checkedAtNo
disclaimerNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Beyond readOnlyHint/openWorldHint it discloses the per-hit payload (list name, aliases, addresses, programs, federal register notice, match score) and, unusually valuably, the cost model: $0.003 per successful call, x402 payment across named networks, and that failed calls are not charged. Billing/auth mechanics are exactly the kind of behavior an agent cannot infer from annotations.

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?

Front-loaded with what the tool does, then results, then the sibling pointer, then price — a sensible order with no filler. The payment clause is slightly over-detailed for a description ('Solana and 10 more networks'), but it is the only place cost is documented, so it earns most of its length.

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?

With annotations, a 100%-covered three-parameter schema, and an output schema all present, the remaining burden is routing, cost, and result shape — and the description covers all three. An agent has everything needed to decide to call it and to anticipate being charged.

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 name, limit, and country are already fully documented with ranges and an ISO-2 example. The description only restates that name is required and country optional, adding no syntax or filtering semantics (e.g., how country interacts with alias matches) beyond the schema.

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 (searches) and a precisely named resource (the US trade.gov Consolidated Screening List) with its constituent lists enumerated in parentheses, plus the name/country input scope. It explicitly separates itself from screen_debarment, so an agent can pick between them without opening either schema.

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 names a concrete alternative (screen_debarment) and the condition that selects it — debarment and exclusion lists — which is real routing guidance. It stops short of stating when this tool is the wrong choice or of any prerequisites beyond payment, so it is clear context rather than a full when/when-not rubric.

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