Skip to main content
Glama
htsapi.dev MCP server

htsapi.dev MCP server

get_ruling

Read-onlyIdempotent

Retrieves one CBP ruling by number with its full text, HTS codes and status, plus any ruling that revoked or modified it, the codes it moved goods to, and the cited notes and GRIs.

Instructions

One CBP ruling: its full text, HTS codes, status and, when revoked or modified, the ruling that did it, the codes it moved the goods to, and the sentence that says so. Codes the current schedule no longer has are listed in obsolete_codes. cites: the explanatory notes, legal notes and GRIs it relies on (heading_scope shows what rulings say a heading covers).

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": {
      "ruling_number": "<ruling_number>"
    },
    "name": "get_ruling"
  }
}

Input Schema

NameRequiredDescriptionDefault
ruling_numberYesA CBP ruling number: N338413, H301540, 881984.

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 declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real semantic context beyond that: revocation/modification chains are surfaced when present, codes absent from the current schedule are segregated into `obsolete_codes`, and `cites` is defined. That is meaningful disclosure of non-obvious result behavior.

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?

Two sentences, front-loaded with the core purpose and followed by field-level notes. The first sentence is a long, gnarled clause ('the ruling that did it, the codes it moved the goods to, and the sentence that says so') that costs some readability, but nothing is 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 annotations covering safety, a fully described single parameter, and an output schema carrying the return shape, the description fills the remaining gaps: what revocations look like, what happens to delisted HTS codes, and what `cites` means. Nothing an agent needs to invoke 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?

There is a single required parameter with 100% schema description coverage, including format examples (N338413, H301540, 881984). The description adds only that the number selects exactly one ruling; the schema already carries the rest, so the baseline 3 applies.

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 description states a specific verb and resource -- fetch one CBP ruling by number -- and enumerates the substantive content returned (full text, HTS codes, status, revocation/modification chain). An agent can immediately tell this is a single-record retrieval rather than a search. It stops short of naming search_rulings or rulings_under_code as the alternatives.

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 by the required ruling_number and the 'One CBP ruling' framing, and there is one useful cross-reference ('heading_scope shows what rulings say a heading covers'). However, it never states when to call this versus search_rulings or rulings_under_code, so the agent must infer the routing from the sibling names alone.

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