Skip to main content
Glama

BRAINIAC Sanctions & Export Control

Look up USML category headings

sanctions-export-control_itar-usml-lookup
Read-onlyIdempotent

Search 22 CFR 121 USML category headings and keywords. Returns category matches only — not an export classification determination. Price $0.04 USDC. POST /api/v1/sanctions-export-control/itar-usml-lookup. 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": {
      "query": "<query>"
    },
    "name": "sanctions-export-control_itar-usml-lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNolimit, integer, from 1 to 21. Required.
queryYesquery, string, length 1 to 200. Required.
categoryNocategory, string, length 1 to 8. Optional.

Output Schema

NameRequiredDescriptionDefault
queryNoquery. String.
matchesNomatches. Array.
sourcesNosources. Array.
limitationsNolimitations. Array.
retrievedAtNoretrievedAt. String.
categoryFilterNocategoryFilter. Null.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare this a safe, read-only, idempotent, open-world lookup, so the description adds real value elsewhere: the $0.04 USDC price, the POST endpoint, and the fact that an unpaid call returns x402 payment terms and does not execute. That payment/auth behavior is exactly what an agent needs and cannot get from annotations.

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 with the scope stated first, followed by the return limitation and the operational details. Nothing is padded, though the endpoint path is somewhat redundant with the tool name.

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?

An output schema exists, so return structure need not be described, and the description still clarifies that results are category matches only. Combined with the payment behavior and the read-only annotations, an agent has everything needed to call this correctly.

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 query, limit, and category are already documented in the schema. The description adds only a loose hint that matching covers headings and keywords, with no detail on category code format or limit behavior, so the baseline of 3 applies.

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 gives a specific verb and resource: search 22 CFR 121 USML category headings and keywords. It also draws a boundary by saying it is not an export classification determination, which implicitly separates it from classification-oriented siblings, though no sibling is named.

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?

The agent learns one important exclusion — this is a heading search, not a classification determination — but gets no explicit statement of when to prefer this over the closely named usml-category-lookup sibling. Usage is implied rather than directed.

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