Skip to main content
Glama

Order: Get Detail

get_order
Read-onlyIdempotent

[Order] [What it does] Reads the details of one DSers order: line items, costs and income, supplier rows, tracking numbers, and the currently saved shipping address and recipient details. [When to use] Use it when the user asks for full order detail, when inspecting Failed or cancelled orders, or when row-level detail is required to repair a blocker, edit an order, or fulfill it. Ordinary Awaiting Order placement uses list_orders summaries and diagnose_order_issue without routine per-order detail reads. Trigger words: this order's detail, its supplier order, what happened with this order. [When not to use] To find orders or see pending volume, use list_orders. To place orders, use place_orders_to_suppliers. For package movement, use get_package_details. It changes nothing. [How to use]

  • dsers_order_id is required and must be the DSers internal order ID from list_orders; a storefront or supplier order number cannot be passed directly.

  • The supplied supplier and tab identify the order to read. The returned items can include items under other suppliers or tabs. If the order details cannot be retrieved, the call returns an error such as NOT_FOUND. Treat omitted optional fields as unavailable, not as zero.

  • supplier_platform_id and tab_status stay required. Copy them from the same list_orders request when that call included them. When list_orders omitted supplier_platform_id or status, copy the omitted field from the same line_items[] row being inspected. Mixed tab_statuses: pick the tab matching the user intent, else the first known value. Do not invent pairs. If tab_statuses is empty, do not call this Tool; re-list with an explicit status.

  • items[].tab_statuses lists only the known memberships for that item. items[].mixed_tab_status=true means more than one known tab; false does not prove completeness.

  • Money uses different bases: income is authoritative in the seller-platform currency, the setting-currency figure may appear only as a labeled conversion, and item prices and supplier costs use the DSers default currency, so never mix them.

  • order.address returns the currently saved shipping address and recipient details, including street address lines, name, phone, email, tax ID, passport numbers, company, and birthday when populated. sales_order_recipient_birthday is returned exactly as stored; AliExpress Brazil rules use DDMMYYYY. Values are returned as stored, without masking; empty fields are omitted. An omitted component does not prove the address is complete or placeable; use diagnose_order_issue before placement. Product titles must be shown verbatim, never translated or truncated. [Side effects] None; read-only. [Confirmation] Not required.

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>",
      "tab_status": "<tab_status>"
    },
    "name": "get_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
tab_statusYesRequired DSers order-tab partition for this lookup. Copy from the same list_orders request status when that call included status; when list_orders omitted status, copy one value from that item's line_items[].tab_statuses. all is rejected.
dsers_order_idYesCopy from orders[].dsers_order_id in list_orders results. Required.
supplier_platform_idYesRequired supplier platform scope for this lookup. Copy from the same list_orders request when that call included supplier_platform_id; when list_orders omitted it, copy line_items[].supplier_platform_id from the item being inspected. Use 0 only for Unmapped.

Output Schema

NameRequiredDescriptionDefault
orderYesNormalized order detail with the currently saved shipping address and recipient details
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.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, destructiveHint=false, idempotentHint and closed-world scope, so safety is covered. The description adds real behavior beyond that: error codes like NOT_FOUND, the rule that omitted optional fields mean unavailable rather than zero, mixed-tab semantics, currency-base separation, and unmasked address data. The 3 reflects how much of this overlaps with the schema rather than gaps; a bit more on partial-failure/large-payload behavior would raise it.

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?

Bold bracketed section headers make it skimmable and the purpose and exclusions are front-loaded, but at roughly 400 words for a three-parameter read it is heavy. The supplier_platform_id/tab_status copy rules largely restate the input-schema descriptions, and the money-basis and verbatim-product-title instructions are operational policy that inflates the definition without helping tool selection.

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?

An output schema exists, yet the description still supplies the interpretive context an agent needs: which currency base is authoritative, that address fields arrive unmasked and may be omitted without proving completeness, and that tab_statuses is a known-membership list rather than an exhaustive one. Nothing needed to call this tool correctly appears to be missing.

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

Parameters5/5

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

Schema coverage is 100%, so the baseline is 3, but the description goes well beyond it by stating that dsers_order_id must be the internal DSers ID and cannot be a storefront or supplier number. It also gives derivation rules for supplier_platform_id and tab_status (copy from the same list_orders request, fall back to the same line_items row, never invent pairs, do not call when tab_statuses is empty), which prevents the most likely invocation error.

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?

"Reads the details of one DSers order" is a specific verb+resource, and the description enumerates what the payload contains (line items, costs and income, supplier rows, tracking numbers, saved address). It explicitly contrasts with list_orders, place_orders_to_suppliers and get_package_details, so an agent can separate it from siblings without opening any schema.

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?

Dedicated When-to-use and When-not-to-use sections state concrete triggering situations (failed/cancelled orders, repairing a blocker) and name the alternative tool for each excluded case. It even declares that ordinary Awaiting Order placement should not use this tool, which is genuine exclusion guidance.

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.