Skip to main content
Glama
redis

Redis Cloud API MCP Server

Official
by redis

get-pro-subscriptions

Retrieve pro subscription details for your Redis Cloud account using the Redis Cloud API MCP Server. Manage resources effectively with straightforward access.

Instructions

Get the pro subscriptions for the current Cloud Redis account

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main handler function for the 'get-pro-subscriptions' tool. It asynchronously calls SubscriptionsProService.getAllSubscriptions() wrapped in executeApiCall and returns the formatted response using createToolResponse.
    "get-pro-subscriptions": async () => {
      const subscriptions = await executeApiCall(
        () => SubscriptionsProService.getAllSubscriptions(),
        "Get pro subscriptions",
      );
      return createToolResponse(subscriptions);
    },
  • Tool schema definition: specifies the tool name, description, and an empty inputSchema (no parameters required).
    const GET_PRO_SUBSCRIPTIONS_TOOL: Tool = {
      name: "get-pro-subscriptions",
      description: "Get the pro subscriptions for the current Cloud Redis account",
      inputSchema: emptySchema,
    };
  • Local registration of the tool within the SUBSCRIPTIONS_PRO_TOOLS array exported from this module.
    export const SUBSCRIPTIONS_PRO_TOOLS = [
      CREATE_PRO_SUBSCRIPTION_TOOL,
      GET_PRO_SUBSCRIPTIONS_TOOL,
      GET_PRO_SUBSCRIPTION_TOOL,
    ];
  • src/index.ts:40-47 (registration)
    Global tool registration: SUBSCRIPTIONS_PRO_TOOLS (including get-pro-subscriptions) is merged into ALL_TOOLS, which is provided to the MCP server's listTools handler.
    const ALL_TOOLS = [
      ...ACCOUNT_TOOLS,
      ...SUBSCRIPTIONS_PRO_TOOLS,
      ...SUBSCRIPTIONS_ESSENTIALS_TOOLS,
      ...TASKS_TOOLS,
      ...DATABASES_PRO_TOOLS,
      ...DATABASES_ESSENTIALS_TOOLS,
    ];
  • src/index.ts:49-56 (registration)
    Global handlers registration: SUBSCRIPTIONS_PRO_HANDLERS (including the handler for get-pro-subscriptions) is merged into ALL_HANDLERS, used by the MCP server's callTool handler to dispatch executions.
    const ALL_HANDLERS = {
      ...ACCOUNT_HANDLERS,
      ...SUBSCRIPTIONS_ESSENTIALS_HANDLERS,
      ...SUBSCRIPTIONS_PRO_HANDLERS,
      ...TASKS_HANDLERS,
      ...DATABASES_PRO_HANDLERS,
      ...DATABASES_ESSENTIALS_HANDLERS,
    };
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 data but does not mention whether it requires authentication, has rate limits, returns paginated results, or details error conditions. This leaves significant gaps for a tool that likely interacts with account data.

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, direct sentence with no wasted words, clearly stating the tool's purpose. It is appropriately sized and front-loaded, making it easy to understand quickly.

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 does not explain what the tool returns (e.g., list of subscriptions, details like status or plans), error handling, or authentication requirements, which are critical for a tool accessing account data.

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 no parameter documentation is needed. The description appropriately does not discuss parameters, aligning with the schema's completeness, though it could note the absence of inputs for clarity.

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 ('pro subscriptions for the current Cloud Redis account'), making the purpose understandable. However, it does not explicitly differentiate from sibling tools like 'get-pro-subscription' (singular) or 'get-essential-subscriptions', leaving some ambiguity about scope.

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 such as 'get-pro-subscription' (singular) or 'get-essential-subscriptions'. It lacks context about prerequisites, timing, or exclusions, offering minimal usage direction.

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