Skip to main content
Glama

MagSnap — Custom Photo Magnets & Gift Printing Store

track_order

Look up order status and shipping progress for an existing MagSnap order by Order ID.

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": {
      "order_id": "<order_id>"
    },
    "name": "track_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
order_idYesThe MagSnap Order ID (UUID format, e.g. 9b1deb4d-3b7d-4bad-9bdd-2b0d7b3dcb6d).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. "Look up" correctly signals a non-mutating read and the phrase "order status and shipping progress" indicates what comes back, but nothing is said about auth requirements, error behavior for invalid or unknown order IDs, rate limits, or freshness of status data.

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?

A single well-formed sentence with the resource and the keying parameter front-loaded and no filler. It could be marginally tighter, but nothing is wasted.

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 one-parameter read tool with full schema coverage and no output schema, the description covers purpose, scope, and the identifying input adequately. The remaining gap is failure/edge-case behavior, which is minor at this complexity level.

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 description coverage is 100% and the schema already documents the UUID format with an example. The description only restates "by Order ID", adding no new meaning 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?

Names a specific verb ("Look up") and a specific resource ("order status and shipping progress" for a MagSnap order), and scopes it by Order ID. It is clearly distinct from the quote/checkout/catalog/FAQ siblings by resource, though it never names them explicitly.

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?

"for an existing MagSnap order" implies a prerequisite (the order must exist and the caller must have its ID), which is useful. But there is no explicit when-to-use/when-not guidance, no statement of what to do when the order ID is unknown, and no routing to any alternative path.

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