Skip to main content
Glama

BRAINIAC Sanctions & Export Control

Screen a name against OFAC non-SDN lists

sanctions-export-control_ofac-non-sdn-screen
Read-onlyIdempotent

Compare a name with the vendored OFAC Consolidated (non-SDN) list: SSI, NS-MBS, CMIC, NS-PLC and CAPTA. SDN screening stays in exclusion.screen. Candidate matches need human review. Price $0.05 USDC. POST /api/v1/sanctions-export-control/ofac-non-sdn-screen. An unpaid call returns the x402 payment terms and does not run.

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": {
      "legalName": "<legalName>"
    },
    "name": "sanctions-export-control_ofac-non-sdn-screen"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNotype, string, one of individual, entity, vessel, any. Required.any
listsNolists, array. Optional.
legalNameYeslegalName, string, length 1 to 300. Required.

Output Schema

NameRequiredDescriptionDefault
queryNoquery. Object.
statusNostatus. String.
matchesNomatches. Array.
sourcesNosources. Array.
snapshotNosnapshot. Object.
limitationsNolimitations. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover the read-only, idempotent, non-destructive profile, and the description adds material context beyond them: a $0.05 USDC price and, importantly, that an unpaid call returns x402 payment terms without executing. It also flags that matches are candidates requiring human adjudication, which shapes how an agent should interpret results.

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?

Four short sentences, front-loaded with the core comparison and list scope, then routing guidance, then the payment caveat. No filler, and the endpoint and price are placed after the substantive content.

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?

With an output schema present, return values need not be explained, and the description covers scope, cost, payment failure behavior, and the human-review requirement. Only the interaction of the optional lists parameter with the default set is left unaddressed.

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 the enum values for type and lists are already documented. The description adds only marginal meaning by naming the five lists the default screening covers; it says nothing about legalName normalization or how the optional lists filter interacts with the default.

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 (compare a name against the OFAC Consolidated non-SDN list) and enumerates the exact constituent lists (SSI, NS-MBS, CMIC, NS-PLC, CAPTA). It also explicitly separates itself from SDN screening, so an agent can route without opening the 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?

Gives a clear when-to-use (non-SDN lists) and a when-not (SDN screening belongs to exclusion.screen), plus a post-call caveat that candidate matches need human review. It does not compare against the other jurisdiction screening siblings, but the scope boundary it does draw is unambiguous.

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