Skip to main content
Glama

BRAINIAC Sanctions & Export Control

Screen a party against the BIS Entity, Denied Persons, Unverified and MEU lists

sanctions-export-control_bis-denied-party-screen
Read-onlyIdempotent

Compare a party name with the vendored BIS rows of the Consolidated Screening List: Entity List, Denied Persons List, Unverified List and Military End-User List. Candidate matches carry addresses, licence requirement and policy and need human review. Price $0.05 USDC. POST /api/v1/sanctions-export-control/bis-denied-party-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_bis-denied-party-screen"
  }
}

Input Schema

NameRequiredDescriptionDefault
listsNolists, array. Optional.
countryNocountry, string. Optional.
legalNameYeslegalName, string, length 1 to 300. Required.

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.5/5.0
Behavior5/5

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

Annotations already cover the read-only, idempotent, non-destructive profile, and the description adds material behavior the annotations cannot: a $0.05 USDC price, the POST path, and the crucial failure mode that an unpaid call returns x402 payment terms and does not execute. It also discloses that matches carry addresses, licence requirement and policy and are advisory only.

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?

Four short sentences, front-loaded with purpose, then match content, then price, then endpoint and payment behavior. Every sentence carries operational information an agent needs; nothing is padded.

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?

With an output schema present, return values need not be explained, and the description nonetheless summarizes what matches contain. Payment preconditions, the failure mode, and the human-review requirement are all covered, leaving no gap an agent would need to discover by trial.

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 description coverage is 100%, so the meaning of legalName, country and the lists enum is already documented. The description names the four list codes in prose but adds no syntax, default, or filtering semantics beyond what the schema provides, which is the expected baseline when the schema does the work.

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 ('Compare a party name with the vendored BIS rows') and enumerates the exact four BIS lists covered, which distinguishes it from the OFAC, EU, AU and CA screening siblings 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 Guidelines4/5

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

The screening context is clear and it explicitly warns that candidate matches 'need human review', which sets the operational stance. It does not, however, state when an agent should prefer a sibling jurisdiction screen (OFAC/EU) or how to combine them, so routing is left mostly to inference from the list names.

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