Skip to main content
Glama
htsapi.dev MCP server

htsapi.dev MCP server

get_notes

Read-onlyIdempotent

Retrieves legally binding HTS section, chapter, subheading, and statistical notes for a code, or General and Additional U.S. Rules of Interpretation when no code is given.

Instructions

The legal text that decides between headings, from the official US schedule. With a code: its section's notes and its chapter's notes, subheading notes, Additional U.S. Notes and statistical notes. These have legal force (GRI 1): they exclude goods from a chapter ("this chapter does not cover...") and define terms. Without a code: the General Rules of Interpretation and the Additional U.S. Rules of Interpretation. The WCO Explanatory Notes are not included (copyrighted); heading_scope gives the passages CBP rulings quote from them.

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": "get_notes"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeNoAny HTS chapter, heading or code (82, 8205, 8205.51.30): its section's and chapter's notes. Leave it out for the General Rules of Interpretation.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, closed-world behavior, and the description goes beyond them by explaining that the returned text carries legal force under GRI 1, that it can exclude goods from a chapter, and that copyrighted Explanatory Notes are deliberately omitted. The only gap is that it says nothing about ordering or how much text is returned, though an output schema exists to cover that.

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?

Three front-loaded sentences with a clear code/no-code split and no filler; the parenthetical '(copyrighted)' and quoted chapter-exclusion example both earn their space. It is dense with tariff jargon ('subheading notes, Additional U.S. Notes and statistical notes'), which is informative but makes the middle sentence heavy.

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?

For a single optional-parameter read tool with rich annotations and an output schema, the description covers the mode semantics, the legal significance of the result, and the scope boundary against sibling tools. Nothing an agent needs in order to call it correctly is missing.

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% and the schema description already explains that `code` accepts any HTS chapter/heading/code and that omitting it yields the General Rules of Interpretation. The description reinforces the omit-case and adds the content difference between modes, but supplies no new format, validation, or granularity detail for the parameter itself.

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

Purpose5/5

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

The description states a specific resource — the legal notes text (section, chapter, subheading, Additional U.S., statistical) from the official US schedule — and explains the two operating modes: with a code vs. without (GRI/AUSRI). It also distinguishes itself from heading_scope by naming what it does not contain (WCO Explanatory Notes, copyrighted) and where that content lives instead.

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

Usage Guidelines5/5

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

Explicit conditional routing: 'With a code... Without a code: the General Rules of Interpretation,' plus a clear exclusion and named alternative ('heading_scope gives the passages CBP rulings quote from them'). An agent knows exactly which call shape produces which content and where to go for the excluded material.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.