Skip to main content
Glama

list_payment_methods

Read-only

Lists saved payment cards and identifies the default so you can choose a valid card for checkout; expired cards are skipped.

Instructions

Saved cards + which is default. Name a card to the user by display_name; card_id is for passing to preview_order/submit_order, never read aloud. Cards ONLY — wallets/gift cards are invisible here; never conclude 'no payment method' from an empty list (offer checkout-url instead). Skip any card with is_expired true.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "intent": "<intent>"
    },
    "name": "list_payment_methods"
  }
}

Input Schema

NameRequiredDescriptionDefault
intentYesOne short line stating who this is for and the goal, e.g. 'Help the user order dinner'. DO NOT include the user's verbatim words, dietary/health/religious details, budgets, names, or other personal specifics — a generic goal is expected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior5/5

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

Annotations only declare readOnly/openWorld; the description adds real behavioral context the schema cannot: expired cards must be skipped, wallets and gift cards are silently absent, and an empty result is not proof of no payment method. It even specifies output-handling rules (read display_name aloud, never card_id), which goes well beyond the annotations.

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?

Four short, front-loaded sentences with zero filler; each one carries a distinct rule (naming, id passing, scope limit, expiry filtering). No repetition of name or annotations.

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

Completeness5/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 conveys the shape of the result (display_name, card_id, default flag, is_expired) and the edge cases an agent must handle. Nothing needed to call or interpret this tool correctly is missing.

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% and the single 'intent' parameter is fully documented there, so the schema carries the semantics. The description never mentions intent or its privacy constraints, so it adds nothing beyond the schema — baseline 3.

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 opening line states the resource and the key payload ('Saved cards + which is default'), and the second sentence names the exact fields returned (display_name, card_id, is_expired). Scope exclusions ('Cards ONLY — wallets/gift cards are invisible here') make it unambiguous against siblings such as set_default_payment_method or get_checkout_url.

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?

It explicitly routes card_id downstream to preview_order/submit_order and tells the agent to offer a checkout-url rather than claim 'no payment method' when the list is empty. It does not contrast itself with set_default_payment_method or state when a listing is even needed, so the when/when-not picture is strong but not complete.

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