Skip to main content
Glama

List payments

list_payments
Read-only

Retrieve a store's payments newest first, one page at a time, with optional status and cursor filters; use it when you need payment history, not for polling.

Instructions

Lists the store's payments in the key's mode, newest first, one page at a time; each leaves out metadata, which get_payment returns. Each call counts toward the account's daily read allowance, so read when you need the answer and never poll in a loop; application code should follow payments with webhooks.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
cursorNonext_cursor from the previous page, with the same status.
statusNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint, but the description adds the traits that actually matter here: newest-first ordering, page-at-a-time pagination, omission of metadata fields, and a per-account daily read quota that each call consumes. The quota and no-polling warning is exactly the operational context an agent cannot get from structured fields.

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?

Two sentences, front-loaded with purpose and scope, then the cost/quota warning, then the alternative pattern. Every clause carries distinct information; nothing is padded.

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 no output schema, the description still tells the agent what comes back (payment records without metadata, paginated) and how to continue paging. It stops short of describing the fields inside a payment or the shape of next_cursor, but the essential contract is covered.

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 coverage is low at 33% — only cursor carries a description — and the prose only implicitly explains pagination via 'one page at a time'. It never clarifies the limit default/max or what the status enum values mean, so a third of the parameter surface remains explained only by the bare 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?

Names a specific verb and resource (list payments) and adds distinguishing scope: the key's mode, newest-first ordering, one page at a time, and metadata omitted. The contrast with get_payment makes the boundary between the two tools unambiguous.

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?

Gives explicit when-to-use (read when you actually need the answer), explicit when-not (never poll in a loop), and names the alternative for the metadata case (get_payment) plus the proper mechanism for ongoing updates (webhooks). Nothing about tool selection is left to inference.

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