Skip to main content
Glama

Calculate US import duty stack

calculate_duty
Read-only

Paid ($0.02/call, needs API key). Full US duty stack for an import: ordinary/FTA duty, Section 232, Section 301 (China lists + 2026 forced-labor action), Section 338, plus MPF and HMF fees. Every line cites its legal source and effective date. Informational only; not customs brokerage or a binding classification.

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": {
      "hts": "<hts>",
      "origin": "<origin>",
      "customs_value": "<customs_value>"
    },
    "name": "calculate_duty"
  }
}

Input Schema

NameRequiredDescriptionDefault
htsYes8- or 10-digit HTSUS code
modeNoocean
unitNoUnit of quantity, e.g. kg, liters, doz, number
originYesCountry of origin, ISO alpha-2 (CN, VN, DE...)
optionsNo
quantityNoQuantity for specific (per-unit) rates
entry_typeNoauto
customs_valueYesCustoms (transaction) value in USD
claim_preferenceNoApply FTA special rate if eligible (goods must qualify as originating)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Read-only and closed-world behavior is already carried by the annotations, so the description earns credit for additions: per-call pricing, an API-key requirement, line-item legal citations with effective dates, and an explicit non-binding/informational disclaimer. It still omits what happens on unsupported HTS codes or missing quantity for specific rates, and says nothing about rate limiting or latency.

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?

Four sentences, front-loaded with the cost and auth prerequisite an agent needs before invoking, then the capability, then the behavioral promise and the legal caveat. No sentence repeats the name or title, and nothing is padding.

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 nine-parameter tool with a nested options object and no output schema, the description covers scope, prerequisites, output character (line items citing legal sources and effective dates), and liability limits. The residual gap is that it never explains the ambiguous options flags or what a returned line item contains structurally.

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?

With 67% schema description coverage the schema carries most parameter meaning, and the description never names a parameter or explains one. It indirectly signals what drives results (origin for Section 301, metal weight for Section 232, mode/entry type for MPF and HMF), but the nested options subfields (auto_part, uk_melted, metal_weight_pct, mhd_vehicle_part) are undocumented in both the schema and the description.

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 names a specific verb and resource and then enumerates the exact computation performed: ordinary/FTA duty, Section 232, Section 301 (including China lists and the 2026 forced-labor action), Section 338, plus MPF and HMF fees. That enumeration makes it unmistakably distinct from hts_lookup and hts_search, which locate codes rather than compute a duty stack.

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 establishes clear context for use: an import with an HTS code, an origin, and a customs value, plus the note that it needs an API key and costs $0.02/call. It also draws a partial boundary with 'Informational only; not customs brokerage or a binding classification,' but never states when to prefer it over a sibling or what to do when the HTS code is unknown.

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