Skip to main content
Glama

Get a CBP ruling

get_ruling
Read-onlyIdempotent

Access: API key required. One CBP CROSS ruling by number (for example N338012 or H313152), the same operation as GET /v1/rulings/{ruling_number}: its date, subject, the HTS codes it cites, the later and earlier rulings CBP lists against it, and, when extracted, the held HTS codes, holding and merchandise description from the ruling text. A ruling binds only the merchandise it was issued for.

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_numberYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety adds little; the description instead earns credit with the API-key access requirement and a scope caveat no annotation covers ('a ruling binds only the merchandise it was issued for'). It also enumerates the returned fields and flags that extracted holding data is conditional ('when extracted').

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One front-loaded sentence: access requirement first, then operation, then payload, then the binding caveat. Every clause adds information an agent needs, and nothing is repetitive.

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?

There is no output schema, and the description compensates by enumerating the returned fields (date, subject, cited HTS codes, cited later/earlier rulings) plus conditional extracted text fields. Together with the access and binding-scope notes, this is sufficient to call and interpret the tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry the parameter, and it does: the value is a CBP CROSS ruling number, with two format examples (letter prefix plus digits) that clarify the pattern without restating it. A slight gap remains on whether the prefix must be a specific letter set.

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 ('One CBP CROSS ruling by number') and pins down scope with concrete example identifiers (N338012, H313152) plus the equivalent REST route. 'One ... by number' implicitly contrasts with the sibling search_rulings, so an agent can tell single-record retrieval from a search operation 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 Guidelines3/5

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

Usage is only implied: the agent must infer that this tool requires already knowing the ruling number, and that search_rulings is the alternative when no number is known. Neither the when-not condition nor the alternative is stated explicitly.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources