Skip to main content
Glama
waka4674

shipsaving-mcp

by waka4674

search_shipments

Search shipments using multiple filters including tracking number, recipient name, status, carrier, and date range.

Instructions

搜索运单列表,支持多种条件筛选

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
shipment_noNo运单号
search_keyNo搜索关键字:支持 shipment id 精确搜索、tracking number 精确搜索、收件人姓名模糊搜索
tracking_noNo追踪号
recipient_nameNo收件人姓名
recipient_cityNo收件人城市
label_print_typeNolabel打印方式:label / qr_code / bar_code
shipment_statusNo运单状态
shipment_status_listNo运单状态(多选,逗号分隔)
tracking_statusNo承运商运单状态
carrier_codeNo承运商代码,如 USPS / UPS
account_idNo承运商账户 ID
provider_idNoProvider ID
store_nameNo店铺名字
store_idNo店铺 ID
first_nameNo收件人名
last_nameNo收件人姓
destination_typeNo收件地址类型:DOMESTIC / INTERNATIONAL
search_start_dateNo创建开始日期,如 2024-11-10T00:00:00Z
search_end_dateNo创建结束日期,如 2024-11-10T00:00:00Z
pageNo页码
page_sizeNo每页数量
Behavior2/5

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

No annotations provided. The description does not disclose behavioral traits such as pagination limits, rate limits, authentication requirements, or what happens when no filters are applied.

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?

A single, direct sentence. Efficiently conveys the core function without redundancy, though it could be slightly more 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?

For a search tool with 21 parameters and no output schema, the description is inadequate. It omits details on return value structure, pagination behavior, and sorting, which are essential for correct usage.

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%, so baseline is 3. The description adds no extra meaning beyond stating that filters are supported. It does not clarify parameter interactions or priorities.

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 explicitly states 'search shipment list' with filtering capabilities, clearly distinguishing from sibling tools like get_shipment_detail or track_shipment.

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 alternatives or which filter combinations to prefer. The description only mentions 'multiple condition filters' without elaboration.

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/waka4674/shipsaving-mcp'

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