Skip to main content
Glama

Order: Cancel Supplier Orders

cancel_supplier_order
Destructive

[Order] [What it does] Requests asynchronous supplier-side cancellation for one DSers order that is in awaiting_payment or awaiting_shipment status; only one order per call. [When to use] Use when the user explicitly wants to stop a specific Agent or 1688 Dropshipping order whose latest confirmed status is awaiting_payment or awaiting_shipment. [When not to use] If status is unknown, check it with get_order first; do not call this for an order in any other status, or for any supplier other than Agent or 1688 Dropshipping. [How to use] Supply exactly one dsers_order_id from list_orders, verified via get_order, the matching required supplier_platform_id for Agent or 1688 Dropshipping, and required status copied from that order (awaiting_payment or awaiting_shipment). Ownership and tab eligibility are checked through Order Core before dispatch. A successful response contains only message: it means DSers acknowledged the asynchronous request, not that cancellation completed. Completion is confirmed only by a later get_order showing the cancelled status. Dispatch once; never auto-retry — re-read order state if the outcome is unclear. [Side effects] May cancel the order's supplier orders; destructive and critical-risk. [Confirmation] Requires explicit, non-skippable user confirmation; show the exact order, supplier, and status first. [Follow-up] After acknowledgement, verify cancellation with get_order; if rejected, report the reason and stop.

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": {
      "dsers_order_id": "<dsers_order_id>",
      "supplier_platform_id": "<supplier_platform_id>",
      "status": "<status>"
    },
    "name": "cancel_supplier_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
statusYesRequired DSers order tab. Copy from list_orders or get_order. Only awaiting_payment and awaiting_shipment are accepted.
dsers_order_idYesExactly one DSers order ID returned by list_orders.
supplier_platform_idYesRequired Agent or 1688 Dropshipping supplier platform ID. Copy from list_orders or get_order. Other platforms are rejected.

Output Schema

NameRequiredDescriptionDefault
messageYesOutcome and safe next step
toolcall_response_atYesUTC timestamp when the Tool response was returned, formatted as RFC3339.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Goes well beyond the destructive/openWorld/idempotent annotations: discloses asynchronous semantics, that a success only means acknowledgement (not completion), the exact response shape, the no-retry rule, confirmation requirements, and side effects. This is rich behavioral context an agent cannot get from annotations alone.

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?

Clearly front-loaded and sectioned with bracketed labels, so the agent can scan. It is somewhat long and repeats the status enumeration in multiple sections, which is minor redundancy rather than padding.

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

Completeness5/5

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

Even though an output schema exists, the description usefully clarifies that a successful response contains only a message and what that message implies. For a destructive, asynchronous mutation tool with 3 required params, nothing essential is missing.

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 coverage is 100% and enums are documented, so baseline is 3. The description adds provenance meaning ('verified via get_order', 'matching required supplier_platform_id', 'exactly one dsers_order_id') that helps the agent choose valid values, though the schema already carries most semantics.

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?

States a specific verb and resource ('Requests asynchronous supplier-side cancellation for one DSers order') plus scope constraints (one order per call, only awaiting_payment/awaiting_shipment). This distinguishes it clearly from sibling tools like get_order and update_order_supplier.

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

Usage Guidelines5/5

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

Explicitly gives when-to-use, when-not-to-use, and named alternatives ('check it with get_order first', 'do not call this for an order in any other status, or for any supplier other than Agent or 1688 Dropshipping'). It also directs the agent to list_orders for sourcing the IDs.

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.