Skip to main content
Glama
Sign In
tariff-resolver

tariff-resolver

by opsloft
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Watch HTS codes for tariff changes

watch_tariff_changes
Idempotent

Track US import tariff changes by saving HTS codes to a watchlist and receiving rate updates whenever official data refreshes, eliminating manual re-checking.

Instructions

Saves HTS codes (with optional origin) to a local watchlist. After each dataset refresh, call check_tariff_updates to see whether the rates on these codes changed. This is how you track 2025-2026 tariff volatility without manual re-checking.

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_codes": "<hts_codes>"
    },
    "name": "watch_tariff_changes"
  }
}

Input Schema

NameRequiredDescriptionDefault
hts_codesYes8-10 digit HTS codes to watch
origin_countryNoShared origin for the shipment (optional)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.0.2
    • changedInput schema / properties / hts_codes / description
      Previous value: -"Danh sách mã HTS 8-10 số cần theo dõi"New value: +"8-10 digit HTS codes to watch"
    • changedInput schema / properties / origin_country / description
      Previous value: -"Xuất xứ chung của lô hàng (tùy chọn)"New value: +"Shared origin for the shipment (optional)"
  2. First observedv1.0.1

TDQS

A4.2/5.0
Behavior4/5

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

Annotations indicate it's a write operation (readOnlyHint=false) and idempotent. The description adds the workflow context (that rates are tracked across dataset refreshes) and specifies the local watchlist, going beyond what the annotations alone convey.

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 concise sentences. The first sentence states the action; the second sentence provides the workflow and context. 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?

The tool is simple (2 params, no output schema), and the description covers the purpose, the workflow (call check_tariff_updates after refresh), and the context (tracking tariff volatility). It doesn't discuss edge cases, but those aren't expected for this simple 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?

The schema already fully documents both parameters with descriptions (100% coverage). The description's mention of 'optional origin' mirrors the schema description for origin_country, adding little novelty. It doesn't compensate beyond the existing schema documentation.

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 uses a specific verb ('Saves') with a clear resource (HTS codes to a watchlist) and scope. It differentiates from siblings like check_tariff_updates by stating this tool does the saving while the sibling does the checking.

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 explicitly states the workflow: save codes first, then call check_tariff_updates after each dataset refresh. This gives clear context for when to use the tool, though it does not explicitly state when not to use it or mention alternative tools for code search/calculation.

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

Deploy Server

Other Tools