Skip to main content
Glama

read_task

Retrieve task details by ID from the taskqueue-mcp server, including tool and rule recommendations to guide task completion for a specified project.

Instructions

Get details of a specific task by its ID. The task may include toolRecommendations and ruleRecommendations fields that should be used to guide task completion.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectIdYesThe ID of the project containing the task (e.g., proj-1).
taskIdYesThe ID of the task to read (e.g., task-1).

Implementation Reference

  • The ToolExecutor for 'read_task' that validates projectId and taskId parameters and retrieves task details via TaskManager.openTaskDetails.
    const readTaskToolExecutor: ToolExecutor = {
      name: "read_task",
      async execute(taskManager, args) {
        // 1. Argument Validation
        const projectId = validateProjectId(args.projectId);
        const taskId = validateTaskId(args.taskId);
    
        // 2. Core Logic Execution
        const resultData = await taskManager.openTaskDetails(projectId, taskId);
    
        // 3. Return raw success data
        return resultData;
      },
    };
  • Tool definition including name, description, and input schema for 'read_task'.
    const readTaskTool: Tool = {
      name: "read_task",
      description: "Get details of a specific task by its ID. The task may include toolRecommendations and ruleRecommendations fields that should be used to guide task completion.",
      inputSchema: {
        type: "object",
        properties: {
          projectId: {
            type: "string",
            description: "The ID of the project containing the task (e.g., proj-1).",
          },
          taskId: {
            type: "string",
            description: "The ID of the task to read (e.g., task-1).",
          },
        },
        required: ["projectId", "taskId"],
      },
    };
  • Registers the readTaskToolExecutor in the global toolExecutorMap used by the tool dispatcher.
    toolExecutorMap.set(readTaskToolExecutor.name, readTaskToolExecutor);
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 mentions the tool retrieves details and notes specific fields (toolRecommendations, ruleRecommendations), but lacks critical information such as whether this is a read-only operation, error handling for invalid IDs, or any rate limits. This leaves gaps in understanding the tool's behavior beyond basic functionality.

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 highly concise and well-structured in two sentences: the first states the core purpose, and the second adds valuable context about specific fields. Every sentence earns its place by providing essential information without redundancy or fluff.

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 moderate complexity (2 required parameters, no output schema, no annotations), the description is adequate but incomplete. It covers the purpose and hints at usage through field mentions, but lacks details on behavioral aspects like error cases or output structure, which are important for a read operation in a task management context.

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, clearly documenting both parameters (projectId and taskId) with examples. The description doesn't add any additional semantic information about the parameters beyond what the schema provides, such as format constraints or relationships between projectId and taskId, so it meets the baseline for high schema coverage.

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 ('Get details') and resource ('a specific task by its ID'), making it easy to understand what the tool does. However, it doesn't explicitly differentiate itself from sibling tools like 'list_tasks' or 'read_project', which would be needed for a perfect score.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage by mentioning that the task includes 'toolRecommendations and ruleRecommendations fields that should be used to guide task completion,' suggesting this tool is for retrieving task details to inform actions. However, it doesn't provide explicit guidance on when to use this versus alternatives like 'list_tasks' for overviews or 'get_next_task' for workflow sequencing.

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/chriscarrollsmith/taskqueue-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server