Skip to main content
Glama

BRAINIAC OFAC & UK Sanctions Screening

Batch screen vendors against OFAC

exclusion_batch-screen

Screen multiple vendors against the official OFAC SDN list. Each vendor is screened independently. Price $0.10 USDC. POST /api/v1/exclusion/batch-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": {
      "vendors": "<vendors>"
    },
    "name": "exclusion_batch-screen"
  }
}

Input Schema

NameRequiredDescriptionDefault
vendorsYes

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 still adds real operational context: it states the price ($0.10 USDC), says unpaid calls return 402 and do not run, and explains that each vendor is screened independently, which tells the agent about partial-result behavior. It stops short of saying whether anything is persisted or what the response contains.

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, all front-loaded and each carrying distinct information: purpose, per-vendor semantics, price, endpoint, and failure behavior. No filler or repetition.

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 is the only place an agent could learn what a screen returns (match/no-match, scores, evidence), and it does not. Payment and scoping are well covered for a simple one-parameter tool, but the result shape is a real gap.

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% and there is one parameter, yet the description only says 'vendors' without explaining that each entry is an object requiring legalName, the 240-character limit, or the 1-25 item cap. The schema is largely self-explanatory from its structure, but the description adds essentially no parameter meaning.

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 uses a specific verb and resource: 'Screen multiple vendors against the official OFAC SDN list', plus 'batch' in the name, so it is clear this is a bulk screen rather than a single screen. It does not explicitly name or rule out the closest sibling (exclusion_multi-list-screen), so differentiation is implied by 'multiple vendors' rather than stated.

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 word 'multiple' implies this tool is for batches, but there is no explicit when-to-use or when-not-to-use guidance, and no mention of exclusion_screen (single vendor) or exclusion_multi-list-screen (other lists) as alternatives. An agent must infer the choice from the name.

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