Skip to main content
Glama
htsapi.dev MCP server

htsapi.dev MCP server

rulings_under_code

Read-onlyIdempotent

Check an HTS code against current and revoked CBP rulings to see how similar goods were classified and whether the classification is in doubt.

Instructions

Every CBP ruling that classifies goods under a code: for checking a code someone already has. rulings are current (not revoked), newest first, or closest to product first, each with what its goods were; moved_away are rulings CBP revoked off this code and the codes the revoking ruling put the goods under. If similar goods were moved away, the code is in doubt.

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

Input Schema

NameRequiredDescriptionDefault
codeYesAn HTS heading, subheading or line, 4 to 10 digits (8205, 8205.51, 8205.51.30.30). Old codes no longer in the schedule work too.
limitNoRulings to return, 1-50.
offsetNoRulings to skip, for the next page.
productNoOptional: the product in plain words, to put the rulings closest to it first.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered by structured data. The description adds no behavior beyond that: it does not mention pagination limits, result caps, or what happens with unroutable/legacy codes in the response. Adequate but thin against a fully annotated tool.

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?

Short and front-loaded with the core definition first, then the use case. Slight redundancy between 'under a code' and 'for checking a code someone already has', but no wasted padding.

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?

With an output schema present, the description need not explain return values, and annotations cover safety. For a 4-parameter filtered lookup the definition is sufficient, though it could note behavior for codes with zero results or how `product` ranking interacts with recency.

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%, including detailed code formatting guidance (4–10 digits, old codes still resolve) and limit/offset/product semantics. The description adds essentially nothing beyond the schema, which is the expected baseline 3 when the schema does the heavy lifting.

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?

States a specific verb and resource ('Every CBP ruling that classifies goods under a code') and adds the intent ('for checking a code someone already has'), which implicitly separates it from text-search siblings like search_rulings. An agent can tell what it returns and what it is not for without opening the schema.

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

Usage Guidelines4/5

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

The phrase 'for checking a code someone already has' gives clear when-to-use context — code-in-hand lookup rather than exploratory search. It does not explicitly name an alternative tool or state exclusions, so it falls short of a 5.

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