warp-agent-mcp

Estimate US Import Duties

international_duty_estimate

Read-only

Estimate US import duties in dollars for the goods on an international shipment, per commodity line, from current tariff rates (base HTS rate plus Section 301 / 232 and other chapter 99 measures). Each line needs a 10-digit HTS code (find it with hs_code_search), the country the goods were made in, and the line's declared value in USD. US imports only. It is an ESTIMATE, not a customs ruling: say so, and say it excludes the merchandise processing fee, harbor maintenance fee, broker fees and any per-unit duty it flags. Use it with international_quote to give the user a landed cost (freight + duty). Auth required; each account has a daily cap.

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": {
      "mode": "<mode>",
      "lines": "<lines>"
    },
    "name": "international_duty_estimate"
  }
}

Input Schema

Name	Required	Description	Default
`mode`	Yes	How the goods arrive: ocean or air
`lines`	Yes	One line per kind of goods

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 2, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations only declare readOnlyHint=true, but the description adds substantial behavioral context: it is an estimate rather than a customs ruling, explicitly excludes MPF, HMF, broker fees, and per-unit duty, and notes that auth is required with a daily cap per account. This gives an agent the caveats it needs to present results correctly.

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 front-loaded with the core purpose, then tightens with input requirements, scope limits, estimate caveats, and companion-tool guidance. Every sentence carries operational value, including the instruction to communicate exclusions to the user.

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 a tool with no output schema, the description explains that results are dollar estimates per commodity line and lists major exclusions, which is enough for correct invocation. It stops short of describing the response structure or whether totals versus per-line breakdowns are returned, leaving a minor gap.

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 the schema already explains mode, hts, origin, value_usd, and line descriptions. The description reinforces the line requirements and the 10-digit HTS format but adds little beyond the schema and does not explain the ocean/air mode parameter.

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?

The description states a specific verb and resource: estimate US import duties in dollars, per commodity line, from current tariff rates. It distinguishes itself from adjacent tools by naming hs_code_search for HTS lookup and international_quote for landed cost, so an agent can identify its role 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 Guidelines5/5

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

It gives explicit usage conditions: US imports only, each line requires a 10-digit HTS code, origin country, and declared USD value. It also names the companion tools and the exact scenario for using this tool: pairing with international_quote to provide a landed cost.

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

All warp-agent-mcp tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.