Skip to main content
Glama

Track one of my orders

track_my_order
Read-onlyIdempotent

Shipping status of one of your own orders: status, carrier, tracking number and link, estimated and actual dates, and the status timeline. If no shipping data is recorded yet, says so.

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": {
      "number": "<number>"
    },
    "name": "track_my_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
numberYesYour order number (from my_orders).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, not open-world), so the bar is lower. The description still adds real value by disclosing the response payload shape and the empty-state behavior ('If no shipping data is recorded yet, says so'), which the annotations do not convey.

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?

Two sentences, front-loaded with the core purpose, then a compact field list and the empty-state caveat. No filler, no restatement of the title, and every clause carries information.

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

Completeness4/5

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

For a single-parameter read tool with full annotation coverage and no output schema, the description gives enough: what it returns and what happens when nothing is recorded. The only gap is the lack of explicit sibling routing, which is minor here.

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% and the single parameter already documents itself ('Your order number (from my_orders)') with a regex pattern. The description adds no format or sourcing detail beyond the schema, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific resource and scope ('Shipping status of one of your own orders') and enumerates exactly what is returned: status, carrier, tracking number and link, estimated/actual dates, and timeline. This clearly separates it from a general order-details call, though it never names the sibling (get_my_order / my_orders) it differs from.

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

Usage Guidelines3/5

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

Usage is only implied: an agent infers it should call this when a user asks 'where is my package'. There is no explicit when-to-use vs get_my_order, no statement of prerequisites beyond the schema, and no exclusions. The 'says so when no data' clause is a behavior note rather than routing 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.

Resources