Skip to main content
Glama
redis

Redis Cloud API MCP Server

Official
by redis

get-database-modules

Retrieve a list of supported database modules (capabilities) for your Redis Cloud account, based on your subscription and database settings.

Instructions

Lookup list of database modules supported in current account (support may differ based on subscription and database settings). These modules are also called capabilities.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the 'get-database-modules' tool. It calls AccountService.getSupportedDatabaseModules() using executeApiCall and wraps the result with createToolResponse.
    "get-database-modules": async () => {
      const modules = await executeApiCall(
        () => AccountService.getSupportedDatabaseModules(),
        "Get database modules",
      );
      return createToolResponse(modules);
    },
  • The Tool object definition for 'get-database-modules', including name, description, and empty input schema.
    const GET_DATABASE_MODULES: Tool = {
      name: "get-database-modules",
      description:
        "Lookup list of database modules supported in current account (support may differ based on subscription and database settings). These modules are also called capabilities.",
      inputSchema: emptySchema,
    };
  • Local registration of the tool schema in the ACCOUNT_TOOLS array.
    export const ACCOUNT_TOOLS = [
      GET_CURRENT_ACCOUNT_TOOL,
      GET_CURRENT_PAYMENT_METHODS_TOOL,
      GET_DATABASE_MODULES,
      GET_PRO_PLANS_REGIONS,
    ];
  • src/index.ts:40-47 (registration)
    Global registration of tools via spread of ACCOUNT_TOOLS into ALL_TOOLS, used in ListToolsRequestHandler.
    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 registration of handlers via spread of ACCOUNT_HANDLERS into ALL_HANDLERS, used in CallToolRequestHandler.
    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?

No annotations are provided, so the description carries the full burden. It mentions that support varies by subscription and settings, which adds some behavioral context about dependencies. However, it lacks details on permissions, rate limits, response format, or error handling, leaving significant gaps for a tool that likely returns account-specific 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, well-structured sentence that efficiently conveys the tool's purpose and key context (subscription/settings dependencies). It avoids redundancy and front-loads essential information, making it highly concise and effective.

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 simplicity (0 parameters, no output schema, no annotations), the description is adequate but has gaps. It explains what the tool does and its dependencies, but without annotations or output schema, it should ideally provide more behavioral details (e.g., response format, error cases) to fully guide an 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 with 100% schema description coverage, so no parameter documentation is needed. The description appropriately focuses on the tool's purpose without redundant parameter details, earning a baseline score of 4 for not introducing unnecessary complexity.

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 with a specific verb ('Lookup list') and resource ('database modules'), and clarifies that these are also called 'capabilities'. It distinguishes the scope as 'supported in current account' with subscription/settings dependencies, though it doesn't explicitly differentiate from sibling tools like 'get-pro-databases' or 'get-essentials-plans'.

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 mentions that support depends on subscription and database settings, which is contextual but doesn't specify use cases, prerequisites, or exclusions compared to sibling tools like 'get-pro-databases' or 'get-essential-subscriptions'.

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