Skip to main content
Glama
redis

Redis Cloud API MCP Server

Official
by redis

get-pro-databases

Retrieve professional databases for a specific subscription ID using Redis Cloud API MCP Server. Manage resources with optional limits and offsets for efficient data handling.

Instructions

Get the pro databases for the provided subscription Id

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoOptional. Maximum number of items to return
offsetNoOptional. Number of items to skip
subscriptionIdYesSubscription ID

Implementation Reference

  • The handler function for the 'get-pro-databases' tool. It extracts and validates the input parameters (subscriptionId, optional offset and limit), calls DatabasesProService.getSubscriptionDatabases API, and returns the formatted response.
    "get-pro-databases": async (request) => {
      const { subscriptionId, offset, limit } = extractArguments<{
        subscriptionId: number;
        offset?: number;
        limit?: number;
      }>(request);
    
      // Validate input
      validateToolInput(
        getProDatabasesSchema,
        { subscriptionId, offset, limit },
        `Get pro databases for subscription: ${subscriptionId}`,
      );
    
      const result = await executeApiCall(
        () =>
          DatabasesProService.getSubscriptionDatabases(
            subscriptionId,
            offset,
            limit,
          ),
        `Get pro databases for subscription: ${subscriptionId}`,
      );
    
      return createToolResponse(result);
    },
  • Zod schema used for input validation in the get-pro-databases handler.
    const getProDatabasesSchema = z.object({
      subscriptionId: commonSchemas.subscriptionId,
      offset: z.number().optional(),
      limit: z.number().optional(),
    });
  • Tool definition for 'get-pro-databases' including name, description, and JSON input schema. This is included in the DATABASES_PRO_TOOLS export array for registration.
    const GET_PRO_DATABASES_TOOL: Tool = {
      name: "get-pro-databases",
      description: "Get the pro databases for the provided subscription Id",
      inputSchema: {
        type: "object",
        properties: {
          subscriptionId: {
            type: "number",
            description: "Subscription ID",
            min: 0,
          },
          offset: {
            type: "number",
            description: "Optional. Number of items to skip",
          },
          limit: {
            type: "number",
            description: "Optional. Maximum number of items to return",
          },
        },
        required: ["subscriptionId"],
      },
    };
  • Export array registering the get-pro-databases tool along with others.
    export const DATABASES_PRO_TOOLS = [
      GET_PRO_DATABASES_TOOL,
      CREATE_PRO_DATABASE_TOOL,
    ];
  • Export of handlers object registering the handler function for get-pro-databases.
    export const DATABASES_PRO_HANDLERS: ToolHandlers = {
      "get-pro-databases": async (request) => {
        const { subscriptionId, offset, limit } = extractArguments<{
          subscriptionId: number;
          offset?: number;
          limit?: number;
        }>(request);
    
        // Validate input
        validateToolInput(
          getProDatabasesSchema,
          { subscriptionId, offset, limit },
          `Get pro databases for subscription: ${subscriptionId}`,
        );
    
        const result = await executeApiCall(
          () =>
            DatabasesProService.getSubscriptionDatabases(
              subscriptionId,
              offset,
              limit,
            ),
          `Get pro databases for subscription: ${subscriptionId}`,
        );
    
        return createToolResponse(result);
      },
      "create-pro-database": async (request) => {
        const payloadArguments = extractArguments<DatabaseCreateRequest>(request);
    
        // Validate input
        validateToolInput(
          databaseCreateRequestSchema,
          payloadArguments,
          `Create pro database using subscription: ${payloadArguments.subscriptionId}`,
        );
    
        const result = await executeApiCall(
          () =>
            DatabasesProService.createDatabase(
              payloadArguments.subscriptionId as never,
              payloadArguments,
            ),
          `Create pro database using subscription: ${payloadArguments.subscriptionId}`,
        );
    
        return createToolResponse(result);
      },
    };
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states a read operation ('Get'), implying it's non-destructive, but doesn't disclose behavioral traits like pagination (implied by limit/offset), authentication needs, rate limits, or return format. For a tool with 3 parameters and no annotations, this leaves significant gaps in understanding how it behaves.

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, efficient sentence with zero waste. It's front-loaded with the core purpose and appropriately sized for the tool's complexity. Every word earns its place without redundancy.

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 no annotations, no output schema, and 3 parameters, the description is incomplete. It lacks details on return values, error conditions, or behavioral context. For a tool that likely returns a list of databases, more information on output structure or usage constraints would be needed for adequate completeness.

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 parameters are fully documented in the schema. The description adds minimal value beyond the schema by mentioning 'subscriptionId' but doesn't explain semantics like what a 'pro database' entails or how limit/offset interact. Baseline 3 is appropriate as the schema does the heavy lifting.

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 databases'), specifying it's for a 'provided subscription Id'. It distinguishes from siblings like 'get-pro-subscriptions' (which lists subscriptions) and 'get-pro-subscription' (which gets a single subscription), but doesn't explicitly contrast them. The purpose is specific but could be more differentiated.

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?

No guidance on when to use this tool versus alternatives like 'get-pro-subscriptions' or 'get-pro-subscription'. The description implies it's for fetching databases under a subscription, but doesn't specify prerequisites, exclusions, or contextual triggers. Usage is inferred rather than explicitly stated.

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