Skip to main content
Glama

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

NameRequiredDescriptionDefault
tnYesTracking number. Copy from list_packages results. Required.

Output Schema

NameRequiredDescriptionDefault
acceptedYesWhether Tracking Core accepted the asynchronous operation
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.7/5.0
Behavior5/5

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

Beyond the annotations it discloses the key behavioral traps: the request is asynchronous, 'accepted' means accepted and not completed, there is no completion flag or refreshed events in the response, stored status may change, and it must be dispatched once with no auto-retry. This is consistent with destructiveHint=false, idempotentHint=false and openWorldHint=true, and adds real context the annotations cannot express.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The bracketed labels front-load purpose, then eligibility, then mechanism, then side effects and follow-up, so an agent can scan to what it needs. Every line carries distinct information; there is no redundant restatement of the name or title.

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 clarifies the semantically misleading part of the response (accepted ≠ completed, no completion flag) and specifies confirmation requirements and the follow-up path. For a one-parameter async mutation tool, nothing an agent needs 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.

Parameters3/5

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

Schema coverage is 100% for the single required parameter, so the schema already documents `tn` fully. The description adds only provenance guidance ('copied from list_packages'), which is useful but marginal, so the baseline of 3 applies.

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 states a specific verb and resource ('requests an asynchronous refresh of carrier tracking status for one tracking number') and immediately bounds the outcome ('does not return refreshed events immediately'). This distinguishes it clearly from the siblings it names, get_package_details and list_packages, without the agent needing to open 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?

It gives an explicit when-to-use ('tracking looks stale and fresh data is needed before reporting progress'), an explicit when-not-to-use naming the correct alternatives for reading current events and finding a tracking number, plus a recovery path ('check get_package_details first if the outcome is unclear'). Nothing about tool selection is left 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.