Skip to main content
Glama
redis

Redis Cloud API MCP Server

Official
by redis

get-task-by-id

Retrieve a specific task by its ID for your Redis Cloud account using the Redis Cloud API MCP Server to manage and monitor task status and details efficiently.

Instructions

Get a task by ID for the current Cloud Redis account

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
taskIdYesTask ID

Implementation Reference

  • Handler function for the 'get-task-by-id' tool. Extracts taskId from request, validates it, calls TasksService.getTaskById, and returns formatted response.
    "get-task-by-id": async (request: ToolRequest) => {
      const { taskId } = extractArguments<{ taskId: string }>(request);
    
      // Validate input
      validateToolInput(commonSchemas.taskId, taskId, "Task ID");
    
      const task = await executeApiCall(
        () => TasksService.getTaskById(taskId),
        `Get task ${taskId}`,
      );
    
      return createToolResponse(task);
    },
  • Tool definition including name, description, and input schema for 'get-task-by-id' requiring a taskId string.
    const GET_TASK_BY_ID_TOOL: Tool = {
      name: "get-task-by-id",
      description: "Get a task by ID for the current Cloud Redis account",
      inputSchema: {
        type: "object",
        properties: {
          taskId: {
            type: "string",
            description: "Task ID",
            minLength: 1,
          },
        },
        required: ["taskId"],
      },
    };
  • Registers the 'get-task-by-id' tool by including it in the exported TASKS_TOOLS array, which is later aggregated in the main server.
    export const TASKS_TOOLS = [GET_TASKS_TOOL, GET_TASK_BY_ID_TOOL];
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 it's a read operation ('Get'), but doesn't mention authentication requirements, rate limits, error handling, or what happens if the task ID is invalid. This leaves significant gaps for a tool that likely interacts with 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, clear sentence with no wasted words. It's front-loaded with the core purpose and efficiently conveys the essential information without unnecessary elaboration.

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?

For a simple read tool with one parameter and no output schema, the description is minimally adequate but lacks depth. It doesn't explain return values, error cases, or account context implications, which could be important given the 'current Cloud Redis account' scope. With no annotations, more behavioral detail would improve 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?

The input schema has 100% description coverage, with 'taskId' documented as 'Task ID'. The description doesn't add any meaning beyond this, such as format examples or constraints. Baseline 3 is appropriate since 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 ('a task by ID for the current Cloud Redis account'), making the purpose understandable. However, it doesn't explicitly differentiate from sibling 'get-tasks' (which likely lists multiple tasks), so it's not fully distinguished from alternatives.

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 is provided on when to use this tool versus alternatives like 'get-tasks' or other sibling tools. The description implies usage for retrieving a specific task by ID but doesn't specify prerequisites, exclusions, or contextual recommendations.

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