Skip to main content
Glama

usitc-tariffs-mcp-server

Browse published HTS chapter headings

usitc_browse_chapter
Read-onlyIdempotent

Browse numbered headings with complete distinct eight-digit rate-line relationships and independent ten-digit statistical counts. A unique combined ten-digit source row can establish an absent eight-digit relationship. Published subchapter titles group following headings when present. Chapters 98 and 99 expose actual published entries without synthetic four-digit headings; grouping is unavailable without sourced markers. Reserved chapters can return a successful empty collection.

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": {
      "chapter": "<chapter>"
    },
    "name": "usitc_browse_chapter"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoDefault 25; 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.
chapterYesChapter 01–99, accepting one or two digits.

Output Schema

NameRequiredDescriptionDefault
pageNoComplete heading collection and continuation.
errorNoPresent when the call failed. Absent on success.
noticeNoActionable next call for this particular empty result, followed by a disclosure when a requested limit above 100 was clamped.
sourceNoSource provenance.
chapterNoNormalized two-digit chapter.
noticesNoPersistent source and coverage limitations.
releaseNoEdition checked for this result.
headingsNoSource-order numbered entries.
totalCountNoComplete locally filtered item count.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • addedInput schema / properties / chapter / pattern
      Added value: +"^\\s*\\d{1,2}\\s*$"
    • 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 25; 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`: Chapter is outside 01–99 or has invalid syntax. `invalid_cursor`: Cursor tool or chapter arguments differ. `cursor_expired`: Original chapter snapshot or edition is unavailable. `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_code`: Chapter is 0 or 00, outside 01–99. `invalid_cursor`: Cursor tool or chapter arguments differ. `cursor_expired`: Original chapter snapshot or edition is unavailable. `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 / 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."
  2. First observed

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already cover readOnly, openWorld, and idempotent, so the safety profile is handled. The description adds genuinely useful behavioral notes: reserved chapters can return a successful empty collection and chapters 98/99 surface real entries rather than synthetic headings. Those are value-adds beyond annotations, though framed in opaque phrasing.

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?

The text is not bloated in length, but it is a single unstructured block of jargon-heavy sentences that resist parsing. Front-loading exists ('Browse numbered headings'), yet the remaining sentences each require re-reading to extract actionable meaning.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 values need not be described. Still, for a browse/list tool the description leaves the actual shape of results ambiguous and leans on unclear terminology. It is adequate but with clear gaps in making the tool's behavior legible to an agent.

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 description coverage is 100%, so the schema already documents chapter, limit, and cursor thoroughly. The description only indirectly touches parameters by referencing chapter numbers (98, 99) and adds no syntax or format detail beyond the schema. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The verb 'Browse' and the resource 'numbered headings' within a chapter are present, so the core action is identifiable. However, most of the description is dense data-model jargon ('eight-digit rate-line relationships', 'ten-digit statistical counts') that obscures rather than clarifies the purpose. It does nothing to distinguish this from siblings like usitc_get_heading or usitc_search_hts.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use guidance and no named alternative. The reader can infer it browses a chapter by number, but nothing says when to prefer this over usitc_search_hts or usitc_get_heading. Only edge-case notes (chapters 98/99, reserved chapters) are given.

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.