Skip to main content
Glama

USTariffRates

Assess one import entry

assess_import_entry

Access: API key required. Assess tariff treatments, AD/CVD cases and import requirements for one entry, the same operation as POST /v1/import-assessments, with the same answer field for field. Only the classification (hts_code, chapters 01-97), origin and entry date are required. Without customs_value_usd every ad valorem amount, subtotal and MPF/HMF estimate is null, the rate expressions are unchanged, and the customs value is listed as a missing calculation input; it is never assumed to be zero. Without requirement_facts each requirement family that depends on them stays pending with the questions to answer; never answer no for an unknown. Omit case_numbers to discover AD/CVD cases from the current Commerce inventory, 20 per page: pass adcvd.discovery.next_cursor as adcvd_cursor with the same entry to continue. Each call is one metered request; reaching the last page does not establish coverage. Adding the customs value or answers later changes the entry, so discovery restarts from the first page. Not a full landed cost, not clearance, and evidence is not verified.

Input Schema

NameRequiredDescriptionDefault
modeNoShipping mode for the standard fee estimate (default ocean).
as_ofYesEntry date in YYYY-MM-DD form.
countryYesISO-2 country code of origin
line_idYesYour identifier for this entry line; part of the entry fingerprint.
hts_codeYesTen-digit HTS classification in chapters 01-97, dotted or undotted.
rule_idsNoRequirement families to screen; omit to screen every family.
quantitiesNoQuantities in the exact units of the reviewed rates, for example { "kg": 120 }; no unit conversions.
adcvd_factsNoDocumented case product and party answers, for example exporter and producer. Omit unknown facts.
descriptionNoProduct description used only to rank discovered cases; not a scope determination.
party_casesNoDocumented company-case assignments per case number, selecting published deposits.
adcvd_cursorNoadcvd.discovery.next_cursor from the previous page, unchanged, with the same entry.
case_numbersNoOfficial AD/CVD case numbers to assess. Omit to discover cases from the current inventory.
tariff_factsNoFacts the entry declares (for example usmca_qualifying, manufacture_year, us_content_share). Structured chapter98 declarations carry valuation, facts, components and evidence. Structured chapter99.exclusion declarations carry a source clause, individual product facts and reference-only documents for the governing 9903.88.69 (note 20(vvv)) or 9903.88.70 (note 20(www)) claim. The section_338_canada declaration carries importation_time and direct_to_consumption_container for the Proclamations 11061–11063 import exclusion (a listed Canadian line imported on or after 12:01 a.m. Eastern time on September 29, 2026 returns error import_prohibited with the determination and no duty total), and the U.S. note 51 facts personal_use_accompanied_baggage, us_content_approved and import_adjustment_offset. general_note_6_eligible decides the note 51(d) civil aircraft exemption from the Section 338 duty. A USMCA claim does not remove the Section 338 duty. The preference declaration (claimed, program, origin_qualified, evidence_on_file, quota_available) claims special tariff treatment on calculate_duty: the preferential rate applies only when all are declared, and the answer is marked as based on the importer's declaration. Unknown keys are rejected by the API. Documentary references are not verified approval.
tariff_claimsNoChapter 98/99 headings the entry claims. Listed but unimplemented treatments return an explicit entry-claim review response, not a duty exemption or total.
customs_value_usdNoFull customs value in US dollars. Omit when not yet known; it is never assumed to be zero.
requirement_factsNoDocumented requirement answers. Omit any you do not know.
destination_statesNoU.S. states (ISO 3166-2) the goods will be sold or distributed in, for their state requirements.
identity_document_referencesNoDigests and transcribed party names of identity documents; references only, not verified.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

No annotations are provided, so the description carries the full disclosure burden. It discloses API-key access, metered per-call billing, null propagation for missing customs value and requirement facts, pagination and restart behavior for AD/CVD discovery, and explicit scope limits such as not being a full landed cost or clearance and not verifying evidence.

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?

The description is dense but well ordered: access and purpose first, then required fields, omitted-value behavior, discovery pagination, metering, and scope limits. Every sentence adds operational information, and there is no filler.

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?

For an 18-parameter assessment tool with no annotations and no output schema, it covers the key invocation behavior and major failure modes. It remains short of fully complete because it does not describe the response shape and misstates the required set by omitting line_id.

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 the baseline is 3. The description adds useful omission semantics for customs_value_usd, requirement_facts, case_numbers and adcvd_cursor, but it also says only hts_code, country and as_of are required even though line_id is required by the schema, creating a potentially misleading required-parameter statement.

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: it assesses tariff treatments, AD/CVD cases and import requirements for one entry. It also scopes the tool with phrases such as 'one entry' and 'not a full landed cost,' but it never names a sibling tool such as calculate_duty or screen_import_requirements, so sibling routing is implicit rather than explicit.

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?

It gives substantive usage conditions: API key required, omit customs_value_usd when unknown, omit requirement_facts when unknown, and omit case_numbers to start AD/CVD discovery. It also explains how to continue with adcvd_cursor, but it does not explicitly say when to choose a sibling tool instead, so full alternative routing is not provided.

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