Skip to main content
Glama

BRAINIAC Sanctions & Export Control

Screen a name against the EU consolidated sanctions list

sanctions-export-control_eu-sanctions-screen
Read-onlyIdempotent

Compare a name with the vendored EU consolidated list of persons, groups and entities subject to EU financial sanctions (every name and alias, all languages). Candidate matches carry the EU reference number, programmes and regulations and need human review. Price $0.05 USDC. POST /api/v1/sanctions-export-control/eu-sanctions-screen. An unpaid call returns the x402 payment terms and does 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": "sanctions-export-control_eu-sanctions-screen"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNotype, string, one of individual, entity, any. Required.any
legalNameYeslegalName, string, length 1 to 300. Required.
programmeNoprogramme, string. Optional.

Output Schema

NameRequiredDescriptionDefault
queryNoquery. Object.
statusNostatus. String.
matchesNomatches. Array.
sourcesNosources. Array.
snapshotNosnapshot. Object.
limitationsNolimitations. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, it discloses that all names and aliases across all languages are searched, that matches carry EU reference numbers, programmes and regulations, that results require human review, and that calls are paid ($0.05 USDC) with unpaid calls returning x402 terms instead of executing. That payment gating is a material behavioral fact annotations cannot express.

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?

Front-loaded with the core action and list scope, followed by result semantics, cost, endpoint and payment fallback. Four sentences with little waste, though the endpoint path and restated title wording are marginally redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists so return shape needn't be explained, and the description still characterizes match contents and the human-review requirement. It omits no-match/empty-result behavior and how match confidence is determined, minor gaps for a screening tool.

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 coverage is 100%, so the schema already documents legalName, type and programme. The description adds only that matching covers every alias and language, with no added meaning for the programme filter or the individual/entity/any distinction. Baseline 3 applies.

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+resource: compare a name against the vendored EU consolidated list of persons, groups and entities subject to EU financial sanctions. The jurisdictional scope (EU list) distinguishes it from the sibling OFAC, AU DFAT, CA SEMA and BIS screens without needing to name them.

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 list scope described; there is no explicit 'use this when screening against EU measures, use X for other jurisdictions'. No prerequisites or exclusions are stated, so an agent must infer selection from 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