Lazada Community MCP

List Recent Orders

list_orders

Read-onlyIdempotent

Retrieve recent orders from your Lazada account to review purchase history and track order status.

Instructions

Use this to read recent orders from the user's Lazada account.

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_orders"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No

Output Schema

Name	Required	Description	Default
`count`	Yes
`orders`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.1Sep 6, 2026

TDQS

A3.7/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, and the description's 'read' is consistent with those. It adds scope information ('recent' orders from the user's account) but does not disclose additional behavior such as default limit, ordering, or session requirements. Given the annotations, this is adequate but not rich.

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 description is a single, direct sentence without filler. It places the action first and conveys the essential purpose immediately, with every word earning its place.

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?

The tool has one optional parameter, clear annotations, and an output schema, so the description does not need to explain return values. It covers the key context of reading orders from the user's account. The only real gap is the undocumented 'limit' parameter, which is minor given the tool's simplicity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

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

Schema description coverage is 0% and the description never mentions the 'limit' parameter. The schema provides only type and min/max constraints, not semantic meaning, and the description does not compensate. An agent must infer that 'limit' caps the number of returned orders, so the description adds zero parameter-level value.

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 action ('read recent orders') and a specific resource ('the user's Lazada account'), which clearly defines the tool's purpose. It is unambiguous and distinct from sibling tools, none of which overlap with listing orders.

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?

The phrase 'Use this to read recent orders...' explicitly tells an agent when to invoke this tool. It does not name alternatives or exclusions, but for a simple list-read operation the context is sufficiently clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.