Skip to main content
Glama

BRAINIAC OFAC & UK Sanctions Screening

Screen a vendor against multiple exclusion lists

exclusion_multi-list-screen

Combine OFAC SDN and UK Sanctions List screening for a single vendor. Matches across lists require human identity review. Price $0.20 USDC. POST /api/v1/exclusion/multi-list/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_multi-list-screen"
  }
}

Input Schema

NameRequiredDescriptionDefault
legalNameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries real weight and delivers: a fixed price of $0.20 USDC, and the explicit failure mode that unpaid calls return 402 and do not execute, plus the human-review requirement on matches. It omits authentication requirements and does not state that the call is a non-mutating lookup, which leaves a small gap.

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?

Four short sentences, front-loaded with purpose, then constraints, price, and endpoint. No filler; the terse fragments (price, path) are functional rather than decorative.

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?

Covers cost, review policy, and failure behavior, but with no output schema and no annotations the description should indicate what a result looks like (match/no-match shape, list attribution) and whether auth is required. For a screening endpoint whose entire value is its result, that is a meaningful omission.

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 0% for the single legalName parameter, and the description says nothing about it — no guidance on exact vs. fuzzy matching, normalization, or how maxLength 240 is enforced. The parameter name is largely self-evident, which keeps this at an adequate rather than poor level.

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 names the specific resource ('a single vendor') and both underlying data sources (OFAC SDN and UK Sanctions List), so an agent can tell this is the combined-screen variant. It stops short of naming the sibling tools (exclusion_screen, exclusion_uk-screen) that would make the distinction explicit.

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?

Mentions screening 'for a single vendor' and that matches need human identity review, which implies the screening workflow. However, it never says when to pick this over exclusion_screen or exclusion_uk-screen, nor when a batch alternative is preferable; the guidance remains inferential.

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