Skip to main content
Glama

Adcvd Orders

adcvd_orders
Read-onlyIdempotent

US antidumping duty (AD) and countervailing duty (CVD) trade-remedy orders, is there an import duty order in place on a product from a country. Searches Federal Register / International Trade Administration notices for a product and/or country, resolves current status per product-country pair (in_place, in_place_revoked_in_part when Commerce revoked an order only for named companies or a carved-out subset, or revoked), and returns AD/CVD case numbers, order type (antidumping, countervailing, or both), and the governing Federal Register notice. Use for "is there an antidumping/countervailing duty order on X from Y", "AD/CVD case number for X", "trade remedy duties on imports of X from Y", "is the dumping order on X still in place". Country matching is forgiving (pass "China", not "the People's Republic of China"). If an HTS code is passed it is used only as a search hint, the ORDER SCOPE LANGUAGE, not any HTS number, governs what merchandise is actually covered, so an HTS mismatch never means "not covered".

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": {
      "country": "China",
      "product": "steel"
    },
    "name": "adcvd_orders"
  }
}

Input Schema

NameRequiredDescriptionDefault
htsNoOptional HTS/HS code as an additional search hint (advisory only, see description)
limitNoMax product/country groups to return (1-50, default 20)
countryNoCountry of origin, e.g. "China", "Vietnam", "South Korea", plain names work
productNoProduct keyword(s), e.g. "steel", "solar cells", "shrimp"

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / country / description
      Previous value: -"Country of origin, e.g. \"China\", \"Vietnam\", \"South Korea\" — plain names work"New value: +"Country of origin, e.g. \"China\", \"Vietnam\", \"South Korea\", plain names work"
    • changedInput schema / properties / hts / description
      Previous value: -"Optional HTS/HS code as an additional search hint (advisory only — see description)"New value: +"Optional HTS/HS code as an additional search hint (advisory only, see description)"
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "country": "China",
      +    "product": "steel"
      +  },
      +  {
      +    "country": "China",
      +    "product": "solar cells"
      +  }
      +]
  3. Changed1 schema field changed
    • removedInput schema / examples
      Removed value: -[
      -  {
      -    "country": "China",
      -    "product": "steel"
      -  },
      -  {
      -    "country": "China",
      -    "product": "solar cells"
      -  }
      -]
  4. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, and the description adds genuinely new behavior: the three resolved statuses including the subtle in_place_revoked_in_part case, the fields returned, and the warning that order scope language rather than any HTS number governs coverage. That last point is a real trap an agent would otherwise fall into.

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 core purpose and query intents, with the HTS caveat placed last where it belongs. Some sentences are long and clause-heavy, but no sentence is filler.

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 enumerates the return payload (case numbers, order type, governing Federal Register notice) and status vocabulary, and it explains the one non-obvious edge case around HTS. Nothing needed to call it correctly is missing.

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 coverage is 100%, so the baseline is 3; the description still adds meaning by explaining how hts is treated (advisory search hint only, an HTS mismatch never means 'not covered') and by telling the agent to pass plain country names. Product/limit semantics are left to the schema.

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?

Names a specific resource (US antidumping/countervailing duty trade-remedy orders) and the concrete question it answers (is there an import duty order on a product from a country). The scope is unambiguous and distinguishable from a case-lookup sibling like adcvd_case.

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 explicit trigger phrasings ("is there an antidumping/countervailing duty order on X from Y", "AD/CVD case number for X") that map directly onto agent intents, plus a note that country matching is forgiving. It stops short of naming when-not-to-use or routing to a sibling tool for case-level detail.

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.