Skip to main content
Glama

BRAINIAC OFAC & UK Sanctions Screening

Screen a vendor against OFAC

exclusion_screen

Compare a vendor name with the official OFAC SDN list. Candidate matches require human review; source unavailability produces WARN. Price $0.15 USDC. POST /api/v1/exclusion/screen. Unpaid calls return 402 and do 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": "exclusion_screen"
  }
}

Input Schema

NameRequiredDescriptionDefault
legalNameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does unusually well: it discloses that matches are candidates needing human review, that source unavailability yields WARN rather than failure, the $0.15 USDC price, and that unpaid calls return 402 without executing. It stops short of stating rate limits, idempotency, or whether a WARN result is still billed.

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?

Five short sentences, front-loaded with the purpose, then review semantics, then cost, endpoint, and payment failure mode. No sentence is filler; the 402 detail in particular prevents a wasted failed call.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description should convey what a response looks like; it covers the match-review and WARN outcomes but not what a clear result returns or what fields accompany a candidate match. Combined with the thin parameter explanation, an agent can invoke it but cannot predict the result shape well.

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 0% for the single parameter, so the description must compensate. It only says 'vendor name', which does not clarify that legalName should be the registered legal entity name, whether normalization is applied or expected, or how truncation at 240 characters is handled.

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 ('Compare a vendor name with the official OFAC SDN list'), and naming the OFAC SDN list implicitly separates it from siblings such as exclusion_uk-screen and exclusion_multi-list-screen. It does not explicitly rule out exclusion_batch-screen, so the sibling differentiation is only partial.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The single-vendor framing ('a vendor name') implies the use case, and the mention that candidate matches require human review hints at the downstream workflow. There is no explicit guidance on when to prefer the batch, multi-list, or UK variants, so the agent must infer the boundaries from the sibling names alone.

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