Skip to main content
Glama

recharge

by io.usefulapi
OverviewDiscussionsAdmin

List charges

recharge_list_charges
Read-only

List charges with optional filters (customer, address, status, ids, purchase item, scheduled/created/updated date ranges) and sorting. Returns { charges }. 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 /charges.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idsNoComma-separated list of charge 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 charge status: success | queued | error | refunded | partially_refunded | skipped | pending_manual_payment | pending.
sort_byNoSort order: id-asc | id-desc | updated_at-asc | updated_at-desc | scheduled_at-asc | scheduled_at-desc.
address_idNoFilter by address id.
customer_idNoFilter by customer id.
scheduled_atNoFilter to charges scheduled on this date (ISO 8601).
created_at_maxNoFilter to charges created on/before this date (ISO 8601).
created_at_minNoFilter to charges created on/after this date (ISO 8601).
updated_at_maxNoFilter to charges updated on/before this date (ISO 8601).
updated_at_minNoFilter to charges updated on/after this date (ISO 8601).
purchase_item_idNoFilter to charges containing this purchase item (subscription/onetime line item) id.
scheduled_at_maxNoFilter to charges scheduled on/before this date (ISO 8601).
scheduled_at_minNoFilter to charges scheduled on/after this date (ISO 8601).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Beyond the readOnlyHint annotation, the description details pagination mechanics, cursor constraints, and return structure ({ charges }), adding significant behavioral context.

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?

Concise, front-loaded with the verb and purpose. The REST endpoint mention is slightly extraneous but not detrimental.

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?

With 15 well-documented parameters and no output schema, the description adequately covers pagination, sorting, and filter combinations; no major gaps.

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%, so baseline is 3. The description reinforces critical cursor behavior and summarizes filter options, adding value beyond the schema.

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 the action ('List charges') and enumerates available filters, distinguishing it from get_charge (single) and other siblings.

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?

Explicitly warns about cursor pagination restriction ('omit every other filter'), but does not explicitly contrast alternatives (e.g., when to use get_charge).

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