Skip to main content
Glama
htsapi.dev MCP server

htsapi.dev MCP server

heading_scope

Read-onlyIdempotent

Retrieve CBP ruling passages, decisions, and legal notes for an HTS heading, prioritized by product, to decide whether a product falls within that heading.

Instructions

What CBP's rulings quote and decide on a heading: for deciding whether a product falls in it. Give the product to get what decides for it first. passages: the lines rulings quote when deciding (mostly from the WCO Explanatory Notes, not published free; fragments, not the whole note), each with the rulings that quote it: their goods, HQ or NY, date, status and what CBP concluded; exclusion marks text on what the heading does not cover. notes_applied: the legal notes rulings applied to the heading. cited_without_quote: rulings that relied on its explanatory note without quoting it. Each passage is as a ruling quotes it.

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": {
      "heading": "<heading>"
    },
    "name": "heading_scope"
  }
}

Input Schema

NameRequiredDescriptionDefault
headingYesAn HTS heading (9505) or any code under it (9505.10.25).
productNoThe product in plain words. Puts first the passages and rulings on goods closest to it: what decides for this product, not what is quoted most.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safe-read profile, and the description goes well beyond them: it discloses that passages come mostly from WCO Explanatory Notes that are not freely published, that they are fragments rather than full notes, and what `exclusion` and `cited_without_quote` signify. These provenance and content caveats are exactly the kind of context annotations cannot carry.

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?

The purpose leads, followed by the parameter hint and then a field-by-field breakdown, so it is front-loaded and dense with useful detail. It is somewhat run-on with semicolon-chained field definitions, and the closing line 'Each passage is as a ruling quotes it' largely repeats the earlier fragment caveat.

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?

The description explains the returned structure's key fields and their provenance even though an output schema exists, which is more than required. Minor gaps remain: nothing says what happens with an unknown heading or zero matching rulings, but nothing essential to invoking the tool 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%, so both parameters are documented without description help, and the description's note that `product` ranks passages by closeness to the goods largely restates the schema text. It adds only modest shading ('what decides for this product, not what is quoted most'), consistent with the 3 baseline.

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 first sentence names a specific resource (what CBP rulings quote and decide on a given HTS heading) and its purpose (classification into that heading). It is distinguishable from siblings like get_ruling or rulings_under_code, though the phrasing 'what decides for it' is idiomatic rather than literal.

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?

Usage is implied: supply a heading, and optionally a product to prioritize results. 'Give the product to get what decides for it first' explains the optional parameter's value, but there is no explicit when-to-use-this-vs-alternative routing, and no sibling tool is named for contrast.

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