Skip to main content
Glama

BRAINIAC Sanctions & Export Control

Look up a Commerce Control List ECCN

sanctions-export-control_ccl-eccn-lookup
Read-onlyIdempotent

Return the Commerce Control List entry text for an ECCN, or ECCN headings matching keywords, from the vendored eCFR 15 CFR part 774 snapshot. Text lookup only, not an export classification. Price $0.04 USDC. POST /api/v1/sanctions-export-control/ccl-eccn-lookup. 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_ccl-eccn-lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
eccnNoeccn, string. Optional.
limitNolimit, integer, from 1 to 50. Required.
queryNoquery, string, length 2 to 200. Optional.

Output Schema

NameRequiredDescriptionDefault
resultsNoresults. Array.
sourcesNosources. Array.
ecfrDateNoecfrDate. String.
snapshotNosnapshot. Object.
limitationsNolimitations. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, open-world and non-destructive behavior, so the description's added value is elsewhere: it discloses the data provenance (a vendored snapshot, implying currency limits), the $0.04 USDC price, the POST transport, and — most importantly — that an unpaid call returns x402 payment terms and does not execute. That payment gating is a real behavioral trait an agent cannot get from annotations or schema.

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 the primary capability before the scope caveat, then pricing and payment behavior. No filler, and the 'not an export classification' disclaimer is placed where it will be read rather than buried.

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-value explanation is unnecessary, and payment/auth behavior is fully covered. The only residual gap is the relationship between the optional 'eccn' and 'query' inputs and how 'limit' interacts with each mode, which an agent may have 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 coverage is 100% and each parameter carries its own pattern/length/range description, so the schema does the heavy lifting and baseline 3 applies. The description implies the usage split between the 'eccn' and 'query' parameters (exact entry retrieval vs. heading keyword matching) but does not state whether they are mutually exclusive or how they combine, leaving that to inference.

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?

Specific verb and resource: 'Return the Commerce Control List entry text for an ECCN, or ECCN headings matching keywords,' with the data source named ('vendored eCFR 15 CFR part 774 snapshot'). The ECCN/text-lookup scope clearly separates it from the screening siblings (OFAC, BIS denied party, EU/CA/AU screens), which check parties rather than return list text.

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?

Explicitly bounds the use case with 'Text lookup only, not an export classification,' which prevents an agent from treating the output as a legal classification determination. It gives clear context but does not name a specific alternative when classification is actually wanted, so it falls just short of a full when/when-not/alternatives 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