Skip to main content
Glama

List my orders

list_my_orders
Read-onlyIdempotent

List the customer's recent Fold orders (most recent first, max 10). If the customer has connected their Fold account to this assistant, returns each order's code, status, dates and address — no email needed. Without a connected account, only says how many recent orders exist (order codes are never revealed from an email alone, for privacy) — use the order code from the customer's confirmation text/email with track_order, or ask them to connect Fold.

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": "list_my_orders"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailNoCustomer email. Only used when the customer has NOT connected their Fold account; then only a count is returned.

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 establish this as a safe read-only, idempotent operation. The description adds meaningful behavioral context beyond annotations: it explains the connected-account condition, privacy constraint that order codes are never revealed from an email alone, max 10 results, sort order, and what fields are returned when connected.

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 description is front-loaded with the core action and scope, and every sentence carries useful routing or behavioral information. It is somewhat dense with parentheticals and repeats part of the email-parameter condition already in the schema, which keeps it from being maximally concise.

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 one-parameter, no-output-schema list tool, the description is complete enough to invoke correctly. It explains both return modes, privacy constraints, result limits, and the alternative path via track_order, leaving no major ambiguity for an agent.

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% and the email parameter already documents that it is only used when the customer has not connected Fold. The description reinforces this conditional meaning and adds the privacy rationale, but it largely repeats schema semantics rather than introducing new parameter syntax or constraints.

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: list the customer's recent Fold orders. It also specifies scope (recent, max 10, most recent first) and distinguishes itself from track_order by explaining that track_order works from an order code. An agent can tell what this tool does and when it differs from the sibling without opening the 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?

The description gives explicit routing logic: if the customer has connected Fold, call this to get order details without email; if not connected, this returns only a count and the agent should use track_order with the confirmation code or ask the customer to connect. Both the preferred path and the fallback are named.

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