Lightspeed X-Series MCP

list_purchase_orders

Read-onlyIdempotent

Retrieves purchase orders from the Lightspeed X-Series account using cursor-based pagination, letting you page through order records to review purchasing activity.

Instructions

Purchase orders (version-cursor paged).

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

Input Schema

Name	Required	Description	Default
`after`	No
`page_size`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Oct 24, 2026

TDQS

C2.3/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so the safety profile is covered. The description adds one genuinely useful behavioral fact — that paging is version-cursor based — but does not explain how the cursor behaves or whether results are stable/ordered.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single short fragment — nothing is wasted, but it is terse to the point of under-specification rather than being efficiently front-loaded information.

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

Completeness2/5

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

An output schema exists so return values needn't be described, but for an openWorld paginated list tool the description should at least explain how to page (what `after` accepts, whether the cursor is a version marker). That critical piece is missing.

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

Parameters2/5

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

Schema description coverage is 0% for both parameters, so the schema only supplies names and defaults (after=0, page_size=100). The phrase "version-cursor paged" hints that `after` is a cursor, but neither parameter's meaning, units, nor iteration semantics are clarified.

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

Purpose2/5

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

"Purchase orders (version-cursor paged)" names the resource but never states the verb (list/retrieve) — it essentially restates the tool name. The only added content is the paging style, so an agent learns little beyond what the name already conveys.

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

Usage Guidelines2/5

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

No guidance on when to use this versus get_purchase_order or other list_* siblings, no mention of filters, and no instructions for what to do with the cursor. Usage is only inferable from the name.

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