Skip to main content
Glama

Tracking: Sync Existing Numbers to Store

sync_existing_tracking_numbers_to_store
Destructive

[Tracking Number / Fulfillment] [What it does] Synchronizes the tracking numbers already stored on one DSers order to the sales channel. After synchronization, the sales channel may automatically update the order's shipment or fulfillment status. [When to use] Use after the supplier has shipped and the DSers order already contains the correct tracking numbers that need to be synchronized to the store. [When not to use] This Tool does not accept new tracking numbers or support selecting specific items. To provide new tracking numbers for selected sales-side items, use update_tracking_numbers_to_store. Use get_package_details to inspect tracking events. Before calling this Tool, use get_order to review the order items and existing tracking numbers. [How to use]

  • Copy dsers_order_id from get_order. Order ownership and currently eligible items are validated before synchronization.

  • Keep switch_fulfillment_service=false for the normal synchronization path.

  • switch_fulfillment_service is supported only for Shopify orders. Set it to true only when normal synchronization fails because the Shopify items are assigned to another fulfillment service and the response explicitly instructs you to switch.

  • Switching the fulfillment service may assign the affected Shopify items to the DSers fulfillment location and affect future orders for those items. Non-Shopify orders must keep this value false.

  • A successful response means only that the synchronization request was accepted. It does not confirm that the sales channel has completed the tracking-number update or fulfillment.

  • This operation is not idempotent. If the outcome is unclear, refresh get_order and the sales-channel order instead of retrying automatically. [Side effects] May update the tracking numbers, shipment status, and fulfillment status of the sales-channel order. The Shopify switch path may also change the fulfillment location assigned to the affected items. [Confirmation] Always required. Before calling this Tool, show and confirm the exact store, order, currently eligible items, existing tracking numbers, selected synchronization path, and any possible Shopify fulfillment-location changes.

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

Input Schema

NameRequiredDescriptionDefault
dsers_order_idYesExactly one DSers order ID. Copy from get_order response. Required.
switch_fulfillment_serviceNoShopify only. Default false uses OnSupplierOrderSendGoods. Set true only after Shopify blocked fulfillment for another fulfillment service; that calls SwitchFulfillmentService, which changes Shopify variant locations to DSers and then fulfills. Non-Shopify orders must keep this false.

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?

Annotations already declare destructive=true and idempotent=false; the description goes further by warning that success means only acceptance of the request, not completed fulfillment, and that retries should be avoided when the outcome is unclear. It also discloses the Shopify-only `switch_fulfillment_service` branch and that it can reassign item fulfillment locations and affect future orders, plus ownership/eligibility validation before execution.

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?

The bracketed section headers (what/when/when-not/how/side effects/confirmation) make it easy to scan and front-load the purpose and alternatives. It is on the long side with some repetition between the description and the schema on `switch_fulfillment_service`, but nearly every line carries operational value.

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?

For a destructive, non-idempotent, open-world mutation with only two parameters and an output schema, the description covers prerequisites, side effects, the confirmation gate, and the acceptance-vs-completion caveat. Nothing an agent needs in order to call it safely 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%, so the baseline is 3, but the description adds a decision rule not fully captured in the schema: `switch_fulfillment_service` should be set true only when normal synchronization fails and the response explicitly instructs switching, and must stay false for non-Shopify orders. It also directs where `dsers_order_id` comes from, though much of this overlaps the schema text.

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: synchronizing already-stored tracking numbers from a DSers order to the sales channel. It explicitly separates itself from `update_tracking_numbers_to_store`, which handles new numbers for selected items, so an agent can choose between them without opening either 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?

Provides explicit when-to-use (after supplier shipment, correct numbers already present), when-not-to-use (no new numbers, no item selection), named alternatives (`update_tracking_numbers_to_store`, `get_package_details`), and a prerequisite (`get_order`). It also imposes a confirmation requirement, leaving little to inference.

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.