Skip to main content
Glama
redis

Redis Cloud API MCP Server

Official
by redis

get-current-payment-methods

Retrieve the payment methods associated with your Redis Cloud account using the Redis Cloud API MCP Server to manage billing and subscription details.

Instructions

Get the current payment methods for the current Cloud Redis account

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main handler function for the 'get-current-payment-methods' tool. It calls the AccountService to fetch payment methods and returns the formatted response.
    "get-current-payment-methods": async () => {
      const paymentMethods = await executeApiCall(
        () => AccountService.getAccountPaymentMethods(),
        "Get current payment methods",
      );
      return createToolResponse(paymentMethods);
    },
  • The Tool schema definition including name, description, and empty input schema.
    const GET_CURRENT_PAYMENT_METHODS_TOOL: Tool = {
      name: "get-current-payment-methods",
      description:
        "Get the current payment methods for the current Cloud Redis account",
      inputSchema: emptySchema,
    };
  • src/index.ts:49-56 (registration)
    Registration of all handlers, including ACCOUNT_HANDLERS which contains the handler for 'get-current-payment-methods', into the main ALL_HANDLERS object used by the MCP server.
    const ALL_HANDLERS = {
      ...ACCOUNT_HANDLERS,
      ...SUBSCRIPTIONS_ESSENTIALS_HANDLERS,
      ...SUBSCRIPTIONS_PRO_HANDLERS,
      ...TASKS_HANDLERS,
      ...DATABASES_PRO_HANDLERS,
      ...DATABASES_ESSENTIALS_HANDLERS,
    };
  • src/index.ts:40-47 (registration)
    Registration of all tools, including ACCOUNT_TOOLS which contains the schema for 'get-current-payment-methods', into the main ALL_TOOLS list provided to the MCP server.
    const ALL_TOOLS = [
      ...ACCOUNT_TOOLS,
      ...SUBSCRIPTIONS_PRO_TOOLS,
      ...SUBSCRIPTIONS_ESSENTIALS_TOOLS,
      ...TASKS_TOOLS,
      ...DATABASES_PRO_TOOLS,
      ...DATABASES_ESSENTIALS_TOOLS,
    ];
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool retrieves payment methods but doesn't mention whether this requires specific permissions, what format the data is returned in, or any rate limits. The description is minimal and lacks details on behavioral traits beyond the basic action.

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?

The description is a single, clear sentence that directly states the tool's purpose without any unnecessary words. It is front-loaded with the key information and efficiently communicates the essential action and resource. There is zero waste in the phrasing.

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

Completeness2/5

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

Given the lack of annotations and output schema, the description is incomplete. It doesn't explain what the return values look like (e.g., list of payment methods, JSON structure) or any error conditions. For a tool that retrieves financial data, more context on behavior and output is needed to be fully helpful to an AI agent.

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?

The tool has 0 parameters, and the schema description coverage is 100%, so there are no parameters to document. The description appropriately doesn't discuss parameters, which is correct for a parameterless tool. This meets the baseline expectation for tools with no parameters.

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?

The description clearly states the action ('Get') and resource ('current payment methods for the current Cloud Redis account'), making the purpose immediately understandable. It doesn't explicitly distinguish from sibling tools like 'get-current-account', but the resource specificity provides adequate differentiation. The description avoids tautology by not just restating the tool name.

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?

The description provides no guidance on when to use this tool versus alternatives like 'get-current-account' or other sibling tools. It doesn't mention prerequisites, such as requiring an active account or authentication. The context is implied (retrieving payment methods), but no explicit usage scenarios or exclusions are provided.

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

Related 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/redis/mcp-redis-cloud'

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