Skip to main content
Glama

List payment methods

list_payment_methods
Read-only

Retrieve payment methods available to an account or country site, optionally filtered by payment type, to select and validate checkout options.

Instructions

List payment methods available to the account or to a country site, optionally filtered by payment type.

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

Input Schema

NameRequiredDescriptionDefault
compactNoReturn id, name, type, status, and amount limits only
site_idNoCountry site (MLA Argentina, MLB Brazil, MLM Mexico, ...). Defaults to the token's site
payment_type_idNoOnly return methods of this type
include_inactiveNoInclude methods whose status is not active

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds the useful scoping fact that results depend on the token's site by default, but says nothing about result volume, pagination, or ordering, which matters for an open-world list endpoint.

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?

A single front-loaded sentence with no filler; the scope and the optional filter are stated in order of importance. It is tight, though it spends its only clause on a filter the schema already explains.

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?

For a read-only, zero-required-parameter list tool with full schema coverage and no output schema, the description covers the essentials of what is listed and over which scope. It leaves gaps on return shape (beyond the compact flag) and on how inactive or unsupported methods are handled, which an agent would want before calling.

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%, so all four parameters (compact, site_id, payment_type_id, include_inactive) are already documented with enums and defaults. The description only restates the site and payment-type filters and adds no syntax or interaction detail beyond the schema, so the baseline 3 applies.

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?

States a specific verb and resource ("List payment methods") plus the two scopes it operates over (account or country site) and the optional type filter. An agent can distinguish it from get_payment (single lookup) and search_payments (transaction search) without opening the schema, though no sibling is named explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the scope wording: use it to enumerate available payment methods for the token's account or a given country site. There is no explicit when-not guidance, no mention of prerequisites (e.g., token scope), and no routing to alternatives such as get_payment for a single method.

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