Skip to main content
Glama

BRAINIAC OFAC & UK Sanctions Screening

Screen a vendor against UK Sanctions List

exclusion_uk-screen

Compare a vendor name with the official UK Sanctions List XML. Candidate matches require human review; source unavailability produces WARN. Price $0.15 USDC. POST /api/v1/exclusion/uk/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_uk-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 still discloses meaningful behavior: matches are advisory and need human review, source failure yields a WARN rather than a hard error, cost is $0.15 USDC, the transport is POST /api/v1/exclusion/uk/screen, and unpaid calls return 402 without executing. It omits the response shape and any rate/retry behavior.

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 the purpose, then operational facts (review requirement, WARN behavior, price, endpoint, 402). Nothing is padded, though the endpoint string is somewhat redundant with the tool's transport metadata.

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?

For a single-parameter screening call with no annotations and no output schema, the definition covers cost, failure semantics, and the human-review requirement well. It still lacks any indication of what a result contains (match score, matched entries) or input normalization expectations, which leaves gaps for an agent planning a call.

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?

One parameter with 0% schema description coverage, so the description must compensate. It clarifies that the input is a vendor/legal name, but adds nothing on formatting, length handling (schema caps at 240), or whether the name should first be normalized via exclusion_normalize.

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?

States a specific verb and resource: 'Compare a vendor name with the official UK Sanctions List XML.' The named list implicitly distinguishes it from siblings like exclusion_multi-list-screen, but it never explicitly says it covers only the UK list or when to prefer the multi-list variant.

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?

Usage is only implied by the resource name (screen a vendor against the UK list). It gives good downstream guidance ('candidate matches require human review', WARN on source unavailability) but offers no explicit when-to-use/when-not or named alternative such as exclusion_multi-list-screen, exclusion_screen, or exclusion_normalize.

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