Skip to main content
Glama

tradepulse

Get global trade intelligence: classify HS codes, calculate landed costs, analyze tariffs, check sanctions, and ensure compliance for cross-border transactions.

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

Input Schema

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

TDQS

C2.9/5.0
Behavior3/5

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

No annotations provided, so description bears full burden. It mentions per-endpoint costs and 'AI-synthesized,' but fails to disclose side effects (e.g., read-only), authentication needs, or data modification behavior. The endpoints seem analytical, but it's not explicit.

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

Conciseness3/5

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

The description is lengthy and includes a truncated first sentence, making it slightly messy. The endpoint list is useful but could be more condensed. Front-loading is moderate; the key idea is present but not optimally structured.

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?

With 26 parameters and no output schema, the description should guide parameter selection per action and explain return values. It does neither. The agent may struggle to determine which parameters are relevant for a given action, reducing completeness.

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 coverage is 100% with detailed parameter descriptions. The description adds some context by listing endpoints with brief explanations, which indirectly clarifies the 'action' parameter. However, it does not add meaning beyond the schema's own descriptions.

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?

The description clearly states 'Global trade intelligence API' and lists many specific trade functions (tariff rates, HS code classification, etc.), making the overall purpose clear. However, the first sentence is truncated and lacks a cohesive statement that this is a unified API routing to multiple endpoints via an 'action' parameter.

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

Usage Guidelines2/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 sibling tools (many other 'pulse' tools). The description does not mention prerequisites, limitations, or alternative scenarios. The agent is left to infer usage from the endpoint list.

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

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/mcp-pulsenetwork'

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