Skip to main content
Glama

usitc-tariffs-mcp-server

Inspect an HTS heading and ancestry

usitc_get_heading
Read-onlyIdempotent

Inspect a four-, six-, eight- or ten-digit HTS classification and its complete indented descendants, including unnamed superior rows. Published section titles are retained separately in sections, outside legal ancestry. Ancestry is built from the whole containing heading before filtering. Each parent and inherited-rate source has an exact nodeId follow-up. Chapters 98 and 99 preserve published forest roots without inventing four-digit records.

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": {
      "code": "<code>"
    },
    "name": "usitc_get_heading"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesFour-, six-, eight- or ten-digit HTS code, bare or conventionally dotted.
limitNoDefault 10; a larger value returns at most 100 items and says so. Keep the same limit when continuing with a cursor.
cursorNoOpaque nextCursor from the same tool with identical arguments.
nodeIdNoExact returned node identifier within this classification subtree; omit to browse.

Output Schema

NameRequiredDescriptionDefault
codeNoCanonical requested code.
pageNoComplete selected subtree and continuation.
errorNoPresent when the call failed. Absent on success.
foundNoWhether the requested classification has published nodes.
nodesNoFlat source-order nodes with legal parents and rate provenance.
noticeNoActionable next call for this particular empty result, followed by a disclosure when a requested limit above 100 was clamped.
rootIdNoFirst selected source node; special chapters can have multiple published roots.
sourceNoSource provenance.
noticesNoPersistent source and coverage limitations.
releaseNoEdition checked for this result.
guidanceNoExecutable research guidance for a successful classification miss.
sectionsNoComplete published section markers from the containing heading, separate from legal ancestry.
totalCountNoComplete locally filtered item count.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed24 schema fields changed
    • changedInput schema / properties / code / description
      Previous value: -"Four-, six- or eight-digit HTS code, bare or conventionally dotted."New value: +"Four-, six-, eight- or ten-digit HTS code, bare or conventionally dotted."
    • addedInput schema / properties / code / pattern
      Added value: +"^\\s*(?:\\d{4}(?:\\d{2}){0,3}|\\d{4}\\.\\d{2}(?:\\.\\d{2}){0,2}|\\d{4}\\.\\d{2}\\.\\d{4})\\s*$"
    • changedInput schema / properties / limit / default
      Previous value: -25New value: +10
    • changedInput schema / properties / limit / description
      Previous value: -"Requested items as a positive safe integer; effectiveLimit discloses clamping to at most 100, and pages may be byte limited. Keep the same requested limit for continuation."New value: +"Default 10; a larger value returns at most 100 items and says so. Keep the same limit when continuing with a cursor."
    • changedOutput schema / properties / error / properties / data / properties / reason / description
      Previous value: -"Machine-readable failure mode. Declared by this tool: `invalid_code`: Code is not a supported four-, six- or eight-digit identifier. `invalid_cursor`: Cursor arguments or node selection do not match this heading. `cursor_expired`: Saved source snapshot or selected edition expired. `release_changed`: Edition changed twice during source assembly. `invalid_hierarchy`: Complete source rows cannot establish safe ancestry. Other values are possible when a failure originates below the handler."New value: +"Machine-readable failure mode. Declared by this tool: `invalid_cursor`: Cursor arguments or node selection do not match this heading. `cursor_expired`: Saved source snapshot or selected edition expired. `release_changed`: Edition changed twice during source assembly. `invalid_hierarchy`: Complete source rows cannot establish safe ancestry. Other values are possible when a failure originates below the handler."
    • changedOutput schema / properties / error / properties / data / properties / reason / examples
      Previous value: -[
      -  "invalid_code",
      -  "invalid_cursor",
      -  "cursor_expired",
      -  "release_changed",
      -  "invalid_hierarchy"
      -]New value: +[
      +  "invalid_cursor",
      +  "cursor_expired",
      +  "release_changed",
      +  "invalid_hierarchy"
      +]
    • changedOutput schema / properties / nodes / items / properties / nodeId / description
      Previous value: -"Release and source-digest-local node identifier."New value: +"Exact node identifier for usitc_get_heading, local to this edition and source export."
    • changedOutput schema / properties / nodes / items / properties / resolvedRates / properties / column2 / properties / sourceFollowUp / description
      Previous value: -"Retrieve the complete rate source and its own parent."New value: +"Inherited only: retrieve the complete rate source and its own parent."
    • changedOutput schema / properties / nodes / items / properties / resolvedRates / properties / column2 / properties / sourceHtsno / description
      Previous value: -"Number on which this rate was published."New value: +"Inherited only: ancestor number on which this rate was published."
    • changedOutput schema / properties / nodes / items / properties / resolvedRates / properties / column2 / properties / sourceNodeId / description
      Previous value: -"Node on which this rate was published."New value: +"Inherited only: ancestor node on which this rate was published."
    • changedOutput schema / properties / nodes / items / properties / resolvedRates / properties / column2 / properties / text / description
      Previous value: -"Unevaluated published rate text."New value: +"Unevaluated rate text; absent when not_published."
    • changedOutput schema / properties / nodes / items / properties / resolvedRates / properties / general / properties / sourceFollowUp / description
      Previous value: -"Retrieve the complete rate source and its own parent."New value: +"Inherited only: retrieve the complete rate source and its own parent."
    • changedOutput schema / properties / nodes / items / properties / resolvedRates / properties / general / properties / sourceHtsno / description
      Previous value: -"Number on which this rate was published."New value: +"Inherited only: ancestor number on which this rate was published."
    • changedOutput schema / properties / nodes / items / properties / resolvedRates / properties / general / properties / sourceNodeId / description
      Previous value: -"Node on which this rate was published."New value: +"Inherited only: ancestor node on which this rate was published."
    • changedOutput schema / properties / nodes / items / properties / resolvedRates / properties / general / properties / text / description
      Previous value: -"Unevaluated published rate text."New value: +"Unevaluated rate text; absent when not_published."
    • changedOutput schema / properties / nodes / items / properties / resolvedRates / properties / special / properties / sourceFollowUp / description
      Previous value: -"Retrieve the complete rate source and its own parent."New value: +"Inherited only: retrieve the complete rate source and its own parent."
    • changedOutput schema / properties / nodes / items / properties / resolvedRates / properties / special / properties / sourceHtsno / description
      Previous value: -"Number on which this rate was published."New value: +"Inherited only: ancestor number on which this rate was published."
    • changedOutput schema / properties / nodes / items / properties / resolvedRates / properties / special / properties / sourceNodeId / description
      Previous value: -"Node on which this rate was published."New value: +"Inherited only: ancestor node on which this rate was published."
    • changedOutput schema / properties / nodes / items / properties / resolvedRates / properties / special / properties / text / description
      Previous value: -"Unevaluated published rate text."New value: +"Unevaluated rate text; absent when not_published."
    • changedOutput schema / properties / notice / description
      Previous value: -"Actionable next call for this particular empty result."New value: +"Actionable next call for this particular empty result, followed by a disclosure when a requested limit above 100 was clamped."
    • removedOutput schema / properties / page / properties / budgetLimited
      Removed value: -{
      -  "description": "True when the complete reply byte budget reduced this page.",
      -  "type": "boolean"
      -}
    • changedOutput schema / properties / page / properties / effectiveLimit / description
      Previous value: -"Applied item ceiling after clamping to 100."New value: +"Requested limit after clamping to 100; every page but the last is full."
    • removedOutput schema / properties / sections / items / properties / nodeId
      Removed value: -{
      -  "description": "Release and source-digest-local node identifier.",
      -  "type": "string"
      -}
    • changedOutput schema / properties / sections / items / required
      Previous value: -[
      -  "nodeId",
      -  "sourceOrdinal",
      -  "indent",
      -  "description",
      -  "publishedRates",
      -  "sourceFields"
      -]New value: +[
      +  "sourceOrdinal",
      +  "indent",
      +  "description",
      +  "publishedRates",
      +  "sourceFields"
      +]
  2. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, openWorld), and the description adds genuine semantic behavior: ancestry is computed from the whole containing heading before filtering, section titles are kept outside legal ancestry, and chapters 98/99 preserve published forest roots. These are non-obvious behaviors an agent could not infer from annotations or schema, though some sentences remain cryptic.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is compact and front-loads the purpose, but several sentences are burdened with unexplained terminology ('published forest roots without inventing four-digit records,' 'inherited-rate source') that costs an agent more to parse than it gains. Tightening and ordering the ancestry rules after the primary action would help.

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-shape explanation is unnecessary, and the description instead covers the tricky semantics (filtering order, section titles, chapter 98/99 handling) and pagination-adjacent follow-ups. Only the missing routing guidance against siblings keeps it from being fully complete for a four-parameter read tool.

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 code formats, limit clamping, cursor reuse and nodeId are already documented in structured data. The description only reinforces nodeId follow-up ('exact nodeId follow-up') without adding format or constraint detail beyond the schema, so the baseline 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 uses a specific verb ('Inspect') and resource ('four-, six-, eight- or ten-digit HTS classification') and scopes the output to 'its complete indented descendants, including unnamed superior rows.' That clearly separates it from a flat search or duty-rate lookup, though the dense domain jargon makes the purpose slower to grasp than it needs to be.

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 workflow is only implied: 'omit to browse' lives in the schema, and the description hints at drill-down via 'Each parent and inherited-rate source has an exact nodeId follow-up.' There is no explicit when-to-use-this vs. search_hts/browse_chapter/lookup_duty_rate guidance or any stated exclusions.

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.