Skip to main content
Glama
TopEase-AI

全球海关贸易数据 MCP

Official
by TopEase-AI

search_customs_data

Query global customs trade data using company name, product keyword, HS code, trade type, country, and date range for import/export analysis.

Instructions

查询海关贸易数据。支持按企业名称(company_name)、产品关键字(product_keyword)、HS编码(hs_code)、贸易时间(date_from/date_to)、进出口类型(trade_type)及原产国(country)进行多维度联合查询。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
company_nameNo企业名称(模糊匹配进口商/出口商名称),会做后置过滤。
product_keywordNo产品描述关键字,例如 "CABIN"、"手机"。
hs_codeNoHS海关编码(前缀匹配),例如 "8415"。
trade_typeNo贸易类型:import(进口)、export(出口)、all(全部,默认)。all
countryNo数据源国(英文名),例如 "Japan"、"China"。
date_fromNo贸易起始日期,格式 YYYY-MM-DD。默认 2025-01-01。
date_toNo贸易结束日期,格式 YYYY-MM-DD。默认当前时间。
page_indexNo页码,默认为1。
page_sizeNo每页记录数,默认为20,最大100。
sort_byNo排序字段,默认 tradedate。支持排序字段;tradedate,quantity,weight,uusdtradedate
sort_orderNo排序方向,asc/desc,默认 desc。desc

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It does not mention whether the tool is read-only, has rate limits, requires authentication, or any side effects. The name implies read operation, but no explicit statement.

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?

The description is two sentences, extremely concise, and front-loads the core purpose. Every word is meaningful, with no redundancy.

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

Completeness3/5

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

Given 11 parameters, full schema coverage, and an output schema, the description is adequate but does not mention output format, pagination, or that all parameters are optional. It could provide higher-level context about result structure.

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%, so baseline is 3. The description enumerates key parameters but adds no new meaning beyond what the schema already provides for each parameter.

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 the tool queries customs trade data and lists specific supported dimensions (company name, product keyword, etc.), providing a specific verb and resource. No sibling tools exist, so differentiation is not required.

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?

The description provides no guidance on when to use this tool, prerequisites, or alternatives. It simply lists capabilities without context for appropriate usage.

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/TopEase-AI/topease-customs-mcp-server'

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