Skip to main content
Glama
redis

Redis Cloud API MCP Server

Official
by redis

get-pro-plans-regions

Retrieve a list of supported regions and cloud providers to manage Redis Cloud resources effectively using the Redis Cloud API MCP Server.

Instructions

Lookup list of regions for cloud provider. These regions include the providers too.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler function for 'get-pro-plans-regions' tool that calls AccountService.getSupportedRegions() to fetch supported regions for pro plans and returns the formatted response.
    "get-pro-plans-regions": async () => {
      const regions = await executeApiCall(
        () => AccountService.getSupportedRegions(),
        "Get pro plans regions",
      );
      return createToolResponse(regions);
    },
  • Tool schema definition for 'get-pro-plans-regions' including name, description ('Lookup list of regions for cloud provider. These regions include the providers too.'), and empty input schema.
    const GET_PRO_PLANS_REGIONS: Tool = {
      name: "get-pro-plans-regions",
      description:
        "Lookup list of regions for cloud provider. These regions include the providers too.",
      inputSchema: emptySchema,
    };
  • Registration of the 'get-pro-plans-regions' tool schema in the exported ACCOUNT_TOOLS array.
    export const ACCOUNT_TOOLS = [
      GET_CURRENT_ACCOUNT_TOOL,
      GET_CURRENT_PAYMENT_METHODS_TOOL,
      GET_DATABASE_MODULES,
      GET_PRO_PLANS_REGIONS,
    ];
  • Registration of the 'get-pro-plans-regions' handler in the exported ACCOUNT_HANDLERS object.
    export const ACCOUNT_HANDLERS: ToolHandlers = {
      "get-current-account": async () => {
        const account = await executeApiCall(
          () => AccountService.getCurrentAccount(),
          "Get current account",
        );
        return createToolResponse(account);
      },
    
      "get-current-payment-methods": async () => {
        const paymentMethods = await executeApiCall(
          () => AccountService.getAccountPaymentMethods(),
          "Get current payment methods",
        );
        return createToolResponse(paymentMethods);
      },
    
      "get-database-modules": async () => {
        const modules = await executeApiCall(
          () => AccountService.getSupportedDatabaseModules(),
          "Get database modules",
        );
        return createToolResponse(modules);
      },
    
      "get-pro-plans-regions": async () => {
        const regions = await executeApiCall(
          () => AccountService.getSupportedRegions(),
          "Get pro plans regions",
        );
        return createToolResponse(regions);
      },
    };
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states it's a lookup (read-only) operation, implying safety, but doesn't cover aspects like rate limits, authentication needs, error handling, or response format. For a tool with zero annotation coverage, this is a significant gap in transparency.

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?

The description is concise with two sentences that directly convey the tool's function and data scope. It's front-loaded with the core purpose, and the second sentence adds useful clarification without waste. A minor deduction to 4 as it could be slightly more structured (e.g., explicitly stating it's a read-only list).

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?

Given the tool's low complexity (0 parameters, no output schema), the description is minimally adequate. It explains what the tool does but lacks details on behavioral traits (e.g., response format, errors) and usage context. Without annotations or output schema, it should do more to compensate, but it meets the basic threshold for a simple lookup tool.

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 schema description coverage is 100%, so there's no need for parameter details in the description. The baseline for 0 parameters is 4, as the description appropriately avoids redundant information and focuses on the tool's purpose.

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 tool's purpose: 'Lookup list of regions for cloud provider.' It specifies the verb ('Lookup') and resource ('regions for cloud provider'), and adds that 'These regions include the providers too,' which clarifies the data scope. However, it doesn't explicitly differentiate from siblings like 'get-essentials-plans' or 'get-pro-databases,' which limits it to a 4.

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. It doesn't mention prerequisites, context (e.g., before creating subscriptions), or exclusions. With siblings like 'get-essentials-plans' and 'get-pro-databases,' the lack of differentiation leaves the agent without clear usage cues.

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