Skip to main content
Glama

recharge

by io.usefulapi
OverviewDiscussionsAdmin

List orders

recharge_list_orders
Read-only

List orders with optional filters (customer, address, subscription, status, ids, created/updated/scheduled date ranges) and sorting. Returns { orders }. Pagination is cursor-based: pass limit (default 50, max 250) and read next_cursor / previous_cursor from the response. IMPORTANT: when paging with cursor, Recharge accepts ONLY limit alongside it — omit every other filter on cursor requests. Recharge REST: GET /orders.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idsNoComma-separated list of order ids to fetch.
limitNoMax results per page (1-250, default 50).
cursorNoPagination cursor (next_cursor / previous_cursor from a prior response). Use it ALONE with `limit` — omit all other filters on cursor requests.
statusNoFilter by order status, e.g. success | queued | error | refunded | skipped | cancelled.
sort_byNoSort order: id-asc | id-desc | created_at-asc | created_at-desc | updated_at-asc | updated_at-desc.
address_idNoFilter by address id.
customer_idNoFilter by customer id.
created_at_maxNoFilter to orders created on/before this date (ISO 8601).
created_at_minNoFilter to orders created on/after this date (ISO 8601).
updated_at_maxNoFilter to orders updated on/before this date (ISO 8601).
updated_at_minNoFilter to orders updated on/after this date (ISO 8601).
subscription_idNoFilter by subscription id.
scheduled_at_maxNoFilter to orders scheduled on/before this date (ISO 8601).
scheduled_at_minNoFilter to orders scheduled on/after this date (ISO 8601).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already indicate readOnlyHint=true. Description adds behavioral details: returns { orders }, cursor-based pagination with limit max 250, and the API endpoint. No contradictions.

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?

Concise, front-loaded with purpose, then pagination details and constraint, ending with API endpoint. Every sentence adds value, no wasted words.

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 list tool with 14 parameters (all documented) and no output schema, the description covers the key aspects: filters, pagination, cursor constraint. Could mention rate limits or response structure, but overall adequate.

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%. Description summarizes filter categories but adds no new semantic meaning beyond what schema already provides. The pagination constraint is useful but pertains to usage, not parameter semantics per se.

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 clearly states 'List orders' (verb+resource) and lists optional filters and sorting, distinguishing it from sibling tools like recharge_get_order or recharge_list_charges.

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?

Provides explicit pagination behavior and the critical constraint that when using cursor, all other filters must be omitted. Does not explicitly mention when not to use, but context is sufficient given sibling differentiation.

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

All recharge toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources