Skip to main content
Glama

Cross Ruling

cross_ruling
Read-onlyIdempotent

Get one CBP CROSS customs ruling letter in full by its ruling number (e.g. "N305619" or "H301481", from cross_search). Returns the complete ruling text, the facts presented, CBP's classification analysis, and the holding, plus the HTS tariff numbers assigned, issue date, and the rulings it modifies, revokes, or is revoked by. Use this to read the actual reasoning behind a tariff classification precedent before relying on it for an entry.

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

Input Schema

NameRequiredDescriptionDefault
max_charsNoTruncate the ruling text to this many characters (default 12000, max 60000). Ruling letters run long.
ruling_numberYesCROSS ruling number, e.g. "N305619". Get one from cross_search.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "ruling_number": "N310725"
      +  }
      +]
  2. Changed1 schema field changed
    • removedInput schema / examples
      Removed value: -[
      -  {
      -    "ruling_number": "N310725"
      -  }
      -]
  3. 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, openWorld, and non-destructive, so the safety profile is covered. The description adds substantive behavior beyond that: what the response contains (full text, facts, classification analysis, holding, HTS numbers, issue date, modification/revocation lineage) and how the ruling relates to others. It does not mention truncation behavior or length limits, which is the main residual gap.

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?

Two sentences, front-loaded with the resource and key, with the second sentence reserved for return contents and rationale. No filler or repetition of the title.

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?

With no output schema, the description fully carries the burden of explaining the return payload, including the analytical sections and related-ruling metadata. Combined with annotations covering safety and the schema covering parameters, an agent has everything needed to call and interpret this tool.

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 both parameters are already documented in the schema. The description reinforces ruling_number with format examples and its provenance from cross_search, but adds nothing about max_chars or truncation; baseline 3 is appropriate.

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 ('Get one CBP CROSS customs ruling letter in full') with the keying parameter ('by its ruling number') and concrete example values. It is clearly distinguishable from cross_search, which is named as the source of the ruling number.

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?

Explicitly frames the use case: read the actual reasoning behind a precedent 'before relying on it for an entry,' and points to cross_search for obtaining the number. It gives a clear positive condition but no explicit when-not-to-use case, keeping it just 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.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.