Skip to main content
Glama
Sign In
tariff-resolver

tariff-resolver

by opsloft
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Check tariff changes between revisions

check_tariff_updates
Read-only

Identify tariff updates by comparing current and previous HTS snapshots, returning changed codes and duty columns with old and new values.

Instructions

Compares the current HTS snapshot with the previously fetched one. Call without codes to check the whole watchlist. Returns each change: code, column (general/special/other/additionalDuties), old → new value.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "check_tariff_updates"
  }
}

Input Schema

NameRequiredDescriptionDefault
hts_codesNoLimit to these codes (default: the watchlist)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.0.2
    • changedInput schema / properties / hts_codes / description
      Previous value: -"Giới hạn vào các mã này (mặc định: watchlist)"New value: +"Limit to these codes (default: the watchlist)"
  2. First observedv1.0.1

TDQS

D1/5.0
Behavior1/5

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

The description fails to reveal any behavioral aspects, and the annotation readOnlyHint=true suggests safe operation, but the description adds no clarity on side effects or authorization needs. Without a description, behavioral transparency is entirely absent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

With zero words, it is concise but lacks substance, making the criterion 'appropriate length relative to purpose'. The description has no structure to evaluate, so it cannot be effective.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 1-parameter helper tool, the description is empty, failing to cover required behaviors like whether it mutates state or how to use it. The description is absent, so it cannot be complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema includes one parameter, but the description gives no insight into its meaning beyond the schema itself. The schema description is decent, but the description should complement it. No added value is provided beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is absent, so it cannot describe the purpose with a verb and resource. It does not differentiate the tool from siblings. The title and name provide some clues, but the description itself is missing.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

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

No guidance on when to use this tool versus alternatives is provided. The description is empty, leaving the AI without instructions on when to invoke it.

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