Skip to main content
Glama
redis

Redis Cloud API MCP Server

Official
by redis

get-current-account

Retrieve details of the active Redis Cloud account to manage resources using the Redis Cloud API MCP Server interface.

Instructions

Get the current Cloud Redis account

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main handler function that implements the logic for the 'get-current-account' tool by calling the AccountService API.
    "get-current-account": async () => {
      const account = await executeApiCall(
        () => AccountService.getCurrentAccount(),
        "Get current account",
      );
      return createToolResponse(account);
    },
  • Schema definition for the tool, specifying name, description, and empty input schema.
    const GET_CURRENT_ACCOUNT_TOOL: Tool = {
      name: "get-current-account",
      description: "Get the current Cloud Redis account",
      inputSchema: emptySchema,
    };
  • src/index.ts:40-47 (registration)
    Registration of all tools by spreading ACCOUNT_TOOLS (which includes get-current-account) into ALL_TOOLS, returned in ListToolsRequest.
    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)
    Registration of all handlers by spreading ACCOUNT_HANDLERS (which includes get-current-account handler) into ALL_HANDLERS, used in CallToolRequest.
    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 a read operation ('Get') but doesn't mention authentication requirements, rate limits, error conditions, or what 'current' implies (e.g., logged-in user's account). This leaves significant gaps in understanding the tool's behavior.

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 with no wasted words. It's front-loaded with the core action and resource, making it efficient and easy to parse. Every word earns its place, achieving optimal conciseness.

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 params, no output schema) and lack of annotations, the description is minimally adequate. It states what the tool does but misses context like authentication needs or return format. For a basic read tool, it's passable but could be more informative to compensate for the missing structured 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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description doesn't add param info, which is fine, but it could have clarified that no inputs are required. Baseline is 4 for zero-param tools, as the schema fully covers the absence of 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 Cloud Redis account'), making the purpose understandable. However, it doesn't differentiate from siblings like 'get-current-payment-methods' or 'get-pro-subscription' beyond specifying the account type, which is adequate but not fully distinguishing.

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-essential-subscriptions' or 'get-pro-subscriptions'. It lacks context about prerequisites, such as authentication needs or whether it's for account info vs. subscription details, leaving usage unclear.

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