Skip to main content
Glama

customers.listPaymentMethods

Retrieve stored payment methods for a Ryft customer to manage billing and payment options.

Instructions

List stored payment methods for a Ryft customer.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes

Implementation Reference

  • Registration and handler implementation for customers.listPaymentMethods tool.
    registerTool(
      'customers.listPaymentMethods',
      'List stored payment methods for a Ryft customer.',
      { id: z.string().min(1) },
      async ({ id }) => client.get(`/customers/${id}/payment-methods`),
    );
Behavior2/5

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

Annotations are absent so description carries full burden. While 'List' implies read-only semantics, the description fails to confirm idempotency, disclose response format, or explain behavior when a customer has no payment methods (empty array vs error).

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?

Single front-loaded sentence with verb-first structure. Efficient length but arguably too terse given the lack of schema annotations and output schema; leaves value on the table by not elaborating on the one parameter.

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

Completeness3/5

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

Adequate for a simple list operation with one parameter, but notable gaps remain: the parameter semantics are implied not stated, no return value description provided, and no differentiation from direct payment method retrieval tools.

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 coverage is 0% requiring description compensation. While 'for a Ryft customer' implies the 'id' parameter is the customer identifier, it does not explicitly confirm this mapping or describe the ID format (UUID, string prefix, etc.), leaving the parameter semantics partially undocumented.

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

Purpose4/5

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

Clear verb 'List' and resource 'stored payment methods' with scope 'for a Ryft customer'. The phrase 'stored payment methods' distinguishes this from customer profile data (siblings customers.get/customers.list) and implies this operates on customer-scoped resources versus paymentMethods.get which operates on specific payment method IDs.

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 paymentMethods.get (which retrieves a specific payment method by its own ID) or prerequisites. No mention of pagination behavior or filtering capabilities.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/bkawk/ryft-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server