Skip to main content
Glama

Track order

track_order
Read-onlyIdempotent

Check the status of any Fold order — works for both hotel-guest pickups and residential pickups. Needs the order code (FOLD-XXXXXX or FHL-XXXXXX) plus the email used when scheduling; with a connected Fold account the email is not needed. Returns current state, a milestone timeline, scheduled dates, items if itemized, and proof-of-delivery photo URL if delivered.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "track_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailNoEmail used when scheduling. Not needed when the customer has connected their Fold account.
orderCodeNoOrder tracking code like FHL-RRKU92 (hotel) or FOLD-K9ZGQ (residential). Optional when the customer has connected their Fold account: omit it to get their most recent order.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / email / description
      Previous value: -"Email used at booking. Not needed when the customer has connected their Fold account."New value: +"Email used when scheduling. Not needed when the customer has connected their Fold account."
  2. Changed2 schema fields changed
    • changedInput schema / properties / orderCode / description
      Previous value: -"Order tracking code like FHL-RRKU92 (hotel) or FOLD-K9ZGQ (residential)"New value: +"Order tracking code like FHL-RRKU92 (hotel) or FOLD-K9ZGQ (residential). Optional when the customer has connected their Fold account: omit it to get their most recent order."
    • changedInput schema / required
      Previous value: -[
      -  "orderCode"
      -]New value: +[]
  3. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already establish read-only, idempotent, non-destructive behavior, and the description goes further by disclosing the authentication model (email vs. connected account) and enumerating what comes back: state, milestone timeline, scheduled dates, items, and proof-of-delivery photo URL. That return-shape disclosure is genuinely valuable because no output schema exists.

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, zero filler, and the core action plus scope are front-loaded before the parameter and return details. Every clause carries information an agent would use.

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 two-optional-param read tool with full schema coverage and no output schema, the description supplies both the prerequisite logic and the return contents. Nothing an agent needs to call it correctly 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 description coverage is 100%, so both parameters are already fully documented, including the FOLD-/FHL- code formats and the connected-account fallback behaviors. The description restates these without adding syntax or edge cases beyond the schema, so baseline 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 verb and resource ("check the status of any Fold order") and explicitly covers both order families, hotel-guest and residential pickups. It does not name the closest sibling (list_my_orders) to draw the boundary between tracking one known order and browsing history, so it stops short of a 5.

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

Usage Guidelines4/5

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

Gives concrete invocation conditions: order code plus scheduling email, with the email unnecessary for connected Fold accounts. It lacks explicit when-to-use-vs-alternatives guidance against list_my_orders or get_receipt, leaving some routing 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.

Resources