Skip to main content
Glama

BRAINIAC OFAC & UK Sanctions Screening

Build an exclusion screening evidence report

exclusion_evidence-report

Screen a vendor name against the official OFAC SDN list and produce a PDF with source status, candidate records, timestamp, and snapshot hash. Matches are not identity confirmations. Price $0.15 USDC. POST /api/v1/exclusion/evidence-report. 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_evidence-report"
  }
}

Input Schema

NameRequiredDescriptionDefault
legalNameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

With no annotations supplied, the description carries the full burden and does so well: it discloses the exact contents of the returned artifact, the critical caveat that matches are not identity confirmations, the cost ($0.15 USDC), the transport (POST /api/v1/exclusion/evidence-report), and the failure mode (402, no execution). Cost and payment side effects are exactly the kind of behavior an agent needs before calling a paid endpoint.

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 with the core action and output front-loaded, followed by the disclaimer, price, endpoint, and payment failure mode. Every sentence carries information an agent needs; no filler or repetition.

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?

For a one-parameter tool with no annotations and no output schema, the description covers the action, the returned artifact's contents, the interpretive caveat, cost, and error behavior. Nothing material is missing for correct invocation.

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?

There is one required parameter (legalName) with 0% schema description coverage, so the description must supply meaning. 'Screen a vendor name' establishes that the input is the vendor's legal name, but nothing is said about format expectations, normalization, or the 240-character limit handled by 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 and resource: screen a vendor name against the official OFAC SDN list, and states the concrete artifact produced (a PDF with source status, candidate records, timestamp, snapshot hash). The combination of single-list scope and PDF evidence output implicitly separates it from exclusion_screen and exclusion_multi-list-screen, so an agent can tell what it does 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 Guidelines3/5

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

The description implies the usage context (an evidence artifact for screening records) and adds important caveats — matches are not identity confirmations, unpaid calls return 402 and do not run. However, it never states when to prefer this over the sibling screening tools (e.g., single-name screen vs multi-list or batch), leaving the agent to infer alternatives 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