Skip to main content
Glama

Starfile

Find a tariff code

search_tariff_codes
Read-onlyIdempotent

Search the U.S. Harmonized Tariff Schedule by product words; returns HTS codes, descriptions and general rates.

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": {
      "query": "<query>"
    },
    "name": "search_tariff_codes"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoSchedule in force on (YYYY-MM-DD).
limitNoMax results (default 10, max 25).
queryYesProduct words, e.g. "frozen shrimp".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds value beyond that by disclosing what the call returns — HTS codes, descriptions and general rates — which is useful since there is no output schema. It says nothing about pagination/truncation behavior or what happens when no match is found.

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?

A single sentence with zero filler; the action and resource are front-loaded and the return values follow immediately. Nothing is repeated or padded.

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 simple three-parameter read-only search with fully documented schema and complete annotations, the description covers purpose and return shape adequately. It stops short of noting result-limit behavior or empty-result handling, which are the only meaningful gaps.

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 every parameter documented including the date format and the limit bounds, so the baseline is 3. The description only reinforces the query parameter with "by product words" and adds no semantics for date or limit beyond what the schema already states.

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

Purpose4/5

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

States a specific verb ("Search") and resource ("U.S. Harmonized Tariff Schedule") plus the input modality ("by product words") and the return payload (HTS codes, descriptions, general rates). It is immediately clear what the tool does, though it offers no explicit differentiation from the closest sibling, tariff_duty.

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

Usage Guidelines3/5

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

Usage is only implied: "by product words" tells the agent the input is a product phrase, which hints at when the tool applies. There is no statement of when not to use it, and no routing to tariff_duty for duty calculation or to anything else for rate lookups once a code is known.

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