Skip to main content
Glama
htsapi.dev MCP server

htsapi.dev MCP server

search_rulings

Read-onlyIdempotent

Find CBP rulings for a product described in plain words, including HTS codes, ruling status, and the product facts CBP used to classify it.

Instructions

CBP rulings for a product described in plain words, by meaning. Each ruling comes with its HTS codes, its status (current, modified, superseded) and the product facts CBP classified. by_code lists the subheadings current rulings point to, in the order of the rulings, each with its HQ rulings, newest ruling and lines: the full codes under it with the rulings for each, which is where the facts that decide between lines show.

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": {
      "query": "<query>"
    },
    "name": "search_rulings"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoRulings to return, 1-30.
queryYesThe product in plain words: what it is, what it is made of, what it is for.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare this a safe, idempotent, closed-world read, so the safety profile is covered. The description adds real behavioral context by enumerating ruling statuses (current, modified, superseded) and the shape of the `by_code` breakdown, but it says nothing about result ranking, relevance behavior, or how semantic matching fails.

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 purpose is front-loaded in the first clause, which is good. But the bulk of the text is a dense, grammatically tangled walkthrough of the `by_code` return structure ('which is where the facts that decide between lines show'), content that an output schema should carry.

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?

With an output schema present, the long return-structure passage is largely redundant, while the genuinely missing pieces — when to prefer this over the code-based siblings, and how many results are relevant — go unaddressed. For a search tool with a semantic-matching premise, that leaves the agent underspecified on selection.

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 baseline is 3; both `query` and `limit` are already documented in the schema. The description contributes one genuinely additive point — that matching is semantic rather than keyword — but never addresses `limit` or what happens at the 1-30 boundary.

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 opening states a concrete resource (CBP rulings) and a concrete retrieval mode (a product described in plain words, matched by meaning), which is specific enough to distinguish it from a code-keyed lookup. It stops short of naming the sibling it contrasts with, so the differentiation is inferred from 'by meaning' rather than stated.

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?

'By meaning' and 'plain words' imply the input is a description rather than an HTS code, which implicitly separates it from rulings_under_code and lookup_hts_code. However, there is no explicit when-to-use statement, no exclusion, and no guidance on when classify_product would be the better call.

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