Skip to main content
Glama

BRAINIAC Sanctions & Export Control

Screen a name or vessel IMO against the Australian sanctions list

sanctions-export-control_au-dfat-screen
Read-onlyIdempotent

Compare a name, or a vessel IMO number, with the vendored DFAT Australian Sanctions Consolidated List. Candidate matches carry the reference, alias strength and measures and need human review. Price $0.05 USDC. POST /api/v1/sanctions-export-control/au-dfat-screen. An unpaid call returns the x402 payment terms and does 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": "sanctions-export-control_au-dfat-screen"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNotype, string, one of individual, entity, vessel, any. Required.any
imoNumberNoimoNumber, string. Optional.
legalNameNolegalName, string, length 1 to 300. 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?

Goes well beyond the annotations: it discloses the result shape (reference, alias strength, measures), that hits are candidates requiring human adjudication, the $0.05 USDC price, and critically that an unpaid call returns x402 payment terms instead of executing. That payment gate is behavior an agent cannot infer from readOnlyHint/idempotentHint.

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 what is compared and what comes back before the operational details. The endpoint URL is somewhat redundant with the tool name but is defensible for a paid HTTP call; nothing else is padding.

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 values need not be spelled out, and the description still flags the payment failure mode, which is the biggest operational risk here. The one gap is that zero parameters are required, yet the description implies a name or IMO must be provided, leaving the empty-call case unexplained.

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 schema already documents type, imoNumber and legalName including the enum and 7-digit pattern. The description only restates the two input modes (name vs IMO) and says nothing about how to set the type discriminator or that at least one of legalName/imoNumber should be supplied.

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 concrete verb (compare/screen) and the exact resource (name or vessel IMO against the vendored DFAT Australian Sanctions Consolidated List). Naming DFAT/Australia distinguishes it from the OFAC, BIS, EU and CA-SEMA siblings without needing to reference 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 implied by the resource and jurisdiction, and the 'need human review' note signals this is a triage step rather than a determination. However, it never says when to choose this list over the sibling screens or what to do when no match is returned, so guidance stays implicit.

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