Skip to main content
Glama

BRAINIAC Tariffs & Trade Reference

Look up a US Schedule B export code

trade-tariff_us-schedule-b-lookup
Read-onlyIdempotent

Look up a 10-digit US Schedule B export code or search Schedule B descriptions in the vendored Census concordance. Not an AES filing. Price $0.02 USDC. POST /api/v1/trade-tariff/us-schedule-b-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": "trade-tariff_us-schedule-b-lookup"
  }
}

Input Schema

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

Output Schema

NameRequiredDescriptionDefault
resultsNoresults. Array.
sourcesNosources. Array.
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?

Annotations already cover read-only, idempotent, open-world and non-destructive, yet the description adds material behavior the agent cannot see elsewhere: a $0.02 USDC cost, x402 payment gating, and the fact that an unpaid call returns payment terms and does not execute. It also identifies the data source as a vendored Census concordance, hinting at snapshot/staleness characteristics.

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 the capability before the cost and transport details. Every sentence carries information, though the raw endpoint path is low-value for an agent compared with the surrounding content.

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?

Payment behavior, data provenance and the two lookup modes are covered, and an output schema exists so return values need no explanation. The one residual gap is that both 'code' and 'query' are optional and the description never says whether they are alternatives or what happens if neither is supplied.

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 10-digit code pattern, query length bounds and limit range. The description reinforces that 'code' is 10-digit and that 'query' searches descriptions, but adds no syntax or format detail beyond the schema, and says nothing about how limit interacts with the two modes.

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?

States a specific verb and resource: look up a 10-digit US Schedule B export code, or search Schedule B descriptions. The scope negative 'Not an AES filing' narrows the purpose further. It does not explicitly contrast with siblings such as the HTS duty-rate lookup, but the resource (Schedule B export code) is named precisely enough to be distinguishable.

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?

Makes the two usage modes clear (exact-code lookup vs. description search) and adds a when-not condition ('Not an AES filing'). It does not name an alternative tool for the excluded case, but the exclusion itself is explicit rather than implied.

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