Skip to main content
Glama

Cross Search

cross_search
Read-onlyIdempotent

Search CBP CROSS, the US Customs and Border Protection ruling letters database, for how Customs has classified a product before. Returns binding and informational ruling letters with ruling number, date, subject, HTS tariff numbers assigned, and whether the ruling was later modified or revoked. Use this to find tariff classification precedent for an import: what HTS code CBP assigned to a similar article, country-of-origin and marking determinations, USMCA/NAFTA eligibility rulings, and valuation rulings. Search by product description ("lithium ion battery pack", "cotton knit shirt"), by HTS code, or by ruling number.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "limit": 5,
      "query": "lithium ion battery pack"
    },
    "name": "cross_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
htsNoOptional HTS/tariff number to narrow the search, e.g. "8507.60.0020".
limitNoMax rulings to return (1-50, default 20).
queryYesProduct description, HTS code, or ruling number, e.g. "lithium ion battery pack" or "8507.60".
sinceNoOnly rulings issued on or after this date (YYYY-MM-DD).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "limit": 5,
      +    "query": "lithium ion battery pack"
      +  },
      +  {
      +    "query": "8507.60"
      +  }
      +]
  2. Changed1 schema field changed
    • removedInput schema / examples
      Removed value: -[
      -  {
      -    "limit": 5,
      -    "query": "lithium ion battery pack"
      -  },
      -  {
      -    "query": "8507.60"
      -  }
      -]
  3. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=true, so safety and side-effect profile are covered. The description adds real value by disclosing what comes back, including the modified/revoked flag, which no structured field conveys. It says nothing about result pagination or whether limit truncates silently, and the openWorld remote-database dependency is left to the annotation.

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?

Front-loaded with the resource and the return shape, then use cases, then query modes — each sentence contributes. It is somewhat long, and the use-case enumeration could be tightened, but nothing is redundant with the schema.

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 no output schema, the description correctly carries the return-value burden by naming the fields and the revocation status. Combined with 100% schema coverage, an agent has what it needs to call this correctly; only pagination/truncation behavior and the relationship to cross_ruling remain open.

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%, so all four parameters are documented in the schema, setting the baseline at 3. The description's line about searching by product description, HTS code, or ruling number adds framing beyond the schema but not new mechanics; the optional hts, since and limit parameters are not mentioned in the description at all.

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?

States a specific verb and resource — "Search CBP CROSS, the US Customs and Border Protection ruling letters database" — and enumerates the return fields (ruling number, date, subject, HTS numbers, modification/revocation status). It never contrasts itself with the sibling cross_ruling, so an agent must infer that this is the discovery/search tool and that one is the single-ruling fetch.

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?

Gives concrete use cases (tariff classification precedent, country-of-origin and marking, USMCA/NAFTA eligibility, valuation), which tells the agent when this tool is the right pick, and lists the three query modes. It stops short of stating when not to use it or naming alternatives such as cross_ruling for fetching a known ruling by number.

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.