Skip to main content
Glama

Starfile

Duty on a tariff code

tariff_duty
Read-onlyIdempotent

The U.S. import duty on an HTS line for goods from a given country on a given date, read from the USITC schedule in force that day: the general or column 2 base rate, special-program rates, and every additional Chapter 99 duty that reaches the code and country (Section 301, Section 232, IEEPA and reciprocal tariffs) with its heading, rate, dates and why it applies. Gives a total only when the schedule settles it, and says why otherwise. Use search_tariff_codes to find a code.

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": {
      "code": "<code>",
      "country": "<country>"
    },
    "name": "tariff_duty"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesHTS line with 8 or 10 digits, e.g. 8471.30.01 or 0306.17.00.
dateNoEntry date; default today (YYYY-MM-DD).
countryYesCountry of origin, ISO two-letter code (CN, MX, DE) or name (China).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the readOnly/idempotent/non-destructive annotations, it discloses real behavioral substance: which rate layers are included, that Chapter 99 duties are reported with heading, rate, dates and rationale, and critically that a total is returned only when the schedule settles it, with an explanation otherwise. That last point sets expectations about partial or indeterminate results that no structured field conveys.

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?

It is front-loaded with the core output statement, then the enumeration of rate layers, then the fallback behavior, then the sibling pointer. The long middle sentence is dense with parenthetical duty programs but each clause carries information; nothing is decorative 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?

With three simple parameters, no nested objects and no output schema, the description carries the burden of describing returns and does so well: rate layers, Chapter 99 detail fields, and conditional total behavior. Minor gaps remain about output formatting and units (currency, per-unit vs ad valorem presentation), which an agent would want to know.

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%, with formats already given for code (8 or 10 digits with examples), date (YYYY-MM-DD, default today) and country (ISO two-letter or name). The description only reinforces the semantics ('HTS line', 'goods from a given country on a given date') without adding syntax or edge-case handling, so the baseline 3 applies.

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+resource: it returns the U.S. import duty on an HTS line for a country on a date, read from the USITC schedule in force that day. It enumerates the components returned (general/column 2 base rate, special-program rates, Chapter 99 duties such as Section 301/232/IEEPA) and names the sibling used for code lookup, so it is distinguishable from search_tariff_codes without opening either schema.

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 explicit routing guidance: 'Use search_tariff_codes to find a code,' which tells the agent the prerequisite step and the alternative for a different need. It stops short of stating when-not-to-use conditions (e.g., non-U.S. destinations or non-import scenarios), so it is clear context rather than full when/when-not coverage.

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