Skip to main content
Glama

BRAINIAC Sanctions & Export Control

Screen a name against the Canadian SEMA sanctions list

sanctions-export-control_ca-sema-screen
Read-onlyIdempotent

Compare a name with the vendored Canada consolidated Special Economic Measures Act (SEMA) sanctions list, including aliases. Candidate matches need human review. Price $0.05 USDC. POST /api/v1/sanctions-export-control/ca-sema-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_ca-sema-screen"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNotype, string, one of individual, entity, vessel, any. Required.any
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

A3.9/5.0
Behavior4/5

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

Annotations already declare this as a read-only, idempotent, open-world, non-destructive operation. The description adds meaningful behavior beyond those annotations: alias matching is included, candidate matches need human review, the call costs $0.05 USDC, and an unpaid call returns x402 payment terms without running.

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?

The description is short, front-loaded, and each sentence carries operational value: the screening action, review caveat, price, endpoint, and unpaid-call behavior. There is no redundant or filler text.

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 simple two-parameter screening tool with an output schema and rich annotations, the description supplies the important context an agent needs: jurisdiction, alias handling, human-review caveat, cost, and payment-gated behavior.

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 the legalName and type parameters, including the enum values and required status. The description adds little parameter-specific meaning beyond clarifying that aliases are considered during name matching.

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: comparing a name against the vendored Canada consolidated SEMA sanctions list, including aliases. It is clearly distinguishable by jurisdiction from sibling tools such as OFAC, EU, AU, and BIS screening tools, though it does not explicitly name an alternative.

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 implied by the Canadian SEMA jurisdiction and the screening operation, but the description does not explicitly say when to use this list rather than another available sanctions screen. It does give useful handling guidance that candidate matches require human review.

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