Skip to main content
Glama

tradepulse

Get tariff rates, classify HS codes, calculate landed costs, analyze FTAs, screen sanctions, and ensure trade compliance with global intelligence.

Instructions

TradePulse: Global trade intelligence API. AI-synthesized tariff rates, HS code classification, FTA duty analysis, landed cost calculation, trade compliance guidance, sanctions screening, market entry analysis, a

Coverage: Global

Endpoints: • classify ($0.10): HS code classification • tariff ($0.10): Tariff rates by HS code and country pair • landed ($0.10): Full landed cost calculator • fta ($0.10): Free Trade Agreement analyzer • sanctions ($0.10): Sanctions and trade restrictions screening • market ($0.10): Market entry intelligence • compliance ($0.10): Export compliance — EAR/ITAR/dual-use • freight-rates ($0.10): Live freight rate intelligence by lane • nearshore ($0.10): Nearshoring and reshoring advisor • supplier-risk ($0.10): Supplier country risk — UFLPA, ESG, and geopolitical • incoterms ($0.10): Incoterms 2020 decoder • news ($0.10): Trade policy intelligence

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesWhich endpoint to call. Options: classify | tariff | landed | fta | sanctions | market | compliance | freight-rates | nearshore | supplier-risk | incoterms | news
langNoResponse language code (en, zh, ja, de, fr, es, ar, hi, etc.)
productNoNatural language product description — e.g. 'laptop computer', 'cotton t-shirts', 'industrial water pump'
hs_codeNo6-digit HS code — e.g. 847130, 610910, 090111
from_countryNoExporting country — e.g. China, Vietnam, Germany, Mexico. Also accepts 'from'
to_countryNoImporting country — e.g. USA, Japan, Germany, Australia. Also accepts 'to'
valueNoDeclared customs value in USD
quantityNoNumber of units (for per-unit cost calculation)
countryNoCountry to screen — e.g. Russia, Iran, Cuba, Myanmar, Belarus
entityNoCompany or individual name to screen
transaction_typeNoexport | import | investment | service
target_countryNoTarget market country. Also accepts 'country' or 'to'
end_useNoStated end-use — affects license requirement
end_userNoEnd-user type or entity name
originNoOrigin port city or country — e.g. Shanghai, Rotterdam, Los Angeles
destinationNoDestination port city or country — e.g. Los Angeles, Hamburg, Sydney
modeNoocean | air | both (default: ocean)
container_typeNo20ft | 40ft | 40hc | lcl (default: 40ft)
current_countryNoCurrent manufacturing/sourcing country — e.g. China, India, Bangladesh
industryNoIndustry or product sector — e.g. electronics, textiles, automotive parts
target_marketNoPrimary market you sell into (default: USA)
priorityNocost | risk | speed | balanced (default: balanced)
sectorNotextiles | electronics | food | chemicals | automotive | mining | any (default: any)
checksNoforced_labor | esg | sanctions | geo_risk | all (default: all)
termNoIncoterms 2020 rule — EXW | FCA | FAS | FOB | CFR | CIF | CPT | CIP | DAP | DPU | DDP
topicNotariffs | fta | sanctions | wto | supply-chain | all
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It lists endpoints with brief descriptions and cost per call, providing some behavioral context. However, it lacks details on error handling, parameter requirements per action, rate limits, or side effects.

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?

The description is well-structured with a summary, coverage note, and bulleted list of endpoints. It front-loads key information but could be slightly more concise without losing detail.

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

Completeness2/5

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

Given the tool's complexity (26 parameters, multiple actions) and no output schema, the description should explain return values and which parameters are required for each action. It does not provide this, leaving significant gaps for agent understanding.

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

Parameters4/5

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

Schema description coverage is 100%, so baseline is 3. The description adds value by listing endpoints with costs and grouping them, which helps understand usage patterns beyond the schema alone.

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 clearly states it is a 'Global trade intelligence API' and lists specific capabilities such as tariff rates, HS code classification, FTA analysis, etc. It distinguishes from sibling tools (many other 'pulse' tools) by focusing on trade intelligence.

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?

The description implies use for trade-related queries but does not explicitly state when to use this tool versus alternatives like 'compliancepulse' or 'marketpulse'. No when-not or alternative guidance is provided.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/GTCC777/pulsenetwork-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server