Skip to main content
Glama

BRAINIAC OFAC & UK Sanctions Screening

Get UK Sanctions List changes

exclusion_uk-changes

Retrieve changes to the UK Sanctions List since a given date, using the official Last Updated field and designation dates. Price $0.05 USDC. POST /api/v1/exclusion/uk/changes. Unpaid calls return 402 and do not run.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "exclusion_uk-changes"
  }
}

Input Schema

NameRequiredDescriptionDefault
sinceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/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 behavioral burden and discloses important details: cost is $0.05 USDC, the endpoint is POST /api/v1/exclusion/uk/changes, and unpaid calls return HTTP 402 and do not run. It does not cover authentication requirements, rate limits, or return format, preventing a higher score.

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?

The definition is short and front-loads the core action, then adds cost, endpoint, and failure behavior in separate sentences. Every sentence contributes useful information, though the HTTP endpoint detail is slightly more operational than necessary for an MCP caller.

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 low-complexity tool with one optional parameter and no output schema, the description covers purpose, data basis, cost, and payment-failure behavior. However, it leaves the 'since' parameter underspecified and does not describe the returned change objects or auth expectations, so an agent could not reliably invoke it without guessing.

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 coverage is 0% and the single optional 'since' parameter has no schema description. The description only repeats 'since a given date' without specifying accepted date formats, timezone expectations, default behavior when omitted, or how the date interacts with Last Updated vs designation dates.

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: retrieve changes to the UK Sanctions List since a given date. It is clearly distinct from screening-oriented siblings by focusing on changes and citing official Last Updated and designation dates, but it does not explicitly differentiate itself from any named alternative.

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

Usage Guidelines2/5

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

The description gives no when-to-use guidance, no exclusions, and no routing to or from alternatives such as exclusion_uk-screen or exclusion_multi-list-screen. The only implied usage is retrieving changes since a date, which is already embedded in the purpose statement.

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