Tracking: Refresh Tracking
sync_supply_order_tracking_number[Tracking / Logistics]
[What it does] Requests an asynchronous refresh of carrier tracking status for one tracking number and syncs it into DSers; does not return refreshed events immediately.
[When to use] Use when a shipment's tracking looks stale and fresh data is needed before reporting progress.
[When not to use] For current tracking events, use get_package_details; to find a tracking number, use list_packages.
[How to use] Supply one tracking number tn copied from list_packages. accepted only means the request was accepted, not completed, and does not show that stored status changed — there is no completion flag or refreshed events in the response. Dispatch once, never auto-retry; check get_package_details first if the outcome is unclear.
[Side effects] May update stored tracking data.
[Confirmation] Required; skippable per authorization policy.
[Follow-up] If refreshed status is still needed, wait and check get_package_details; if rejected, report the message 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": {
"tn": "<tn>"
},
"name": "sync_supply_order_tracking_number"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| tn | Yes | Tracking number. Copy from list_packages results. Required. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| accepted | Yes | Whether Tracking Core accepted the asynchronous operation | |
| toolcall_response_at | Yes | UTC timestamp when the Tool response was returned, formatted as RFC3339. |