Skip to main content
Glama

BRAINIAC Sanctions & Export Control

Look up United States Munitions List text

sanctions-export-control_usml-category-lookup
Read-onlyIdempotent

Return the USML (22 CFR 121.1) text for a category or paragraph, or paragraphs matching keywords, from the vendored eCFR snapshot. Not a jurisdiction or classification determination. Price $0.04 USDC. POST /api/v1/sanctions-export-control/usml-category-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_usml-category-lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNolimit, integer, from 1 to 50. Required.
queryNoquery, string, length 2 to 200. Optional.
categoryNocategory, string. 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.3/5.0
Behavior5/5

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

Beyond the read-only and idempotency annotations, it discloses the $0.04 USDC price and that an unpaid call returns x402 payment terms without executing. The vendored-snapshot source and legal-determination disclaimer add further operational context, although snapshot freshness is not stated.

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 purpose and source are front-loaded, followed by the legal limitation, price, endpoint, and payment behavior in compact sentences. Nearly every phrase supplies invocation-relevant information, with no filler.

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?

Together with the annotations, structured input schema, and output schema, this provides enough information for most correct calls. The main remaining gaps are snapshot currency, parameter interaction and empty-request behavior, and selection guidance relative to the similarly named ITAR/USML sibling.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Although schema coverage is 100%, its parameter descriptions are mostly generic; the description usefully clarifies that category can identify a category or paragraph and that query performs keyword matching over paragraphs. It does not explain limit's result scope, whether category and query can be combined, or what an entirely empty request returns.

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 specifies the operation and resource: returning USML (22 CFR 121.1) text by category or paragraph, or finding paragraphs by keyword, from a vendored eCFR snapshot. This distinguishes it from party-screening and CCL tools, but it does not explicitly differentiate the similarly named ITAR/USML lookup sibling.

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 lookup modes imply when to use the tool, and 'Not a jurisdiction or classification determination' establishes a clear when-not boundary. It does not identify an alternative for those determinations or explain when to prefer the sibling ITAR/USML lookup.

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