Skip to main content
Glama

open_task_details

Retrieve detailed information about a specific task by providing its task ID. Use this to inspect task status, requirements, and progress within the TaskFlow MCP task management system.

Instructions

Get details of a specific task by 'taskId'. This is for inspecting task information at any point.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
taskIdYes

Implementation Reference

  • The MCP tool handler function. It extracts the taskId from input arguments and delegates execution to the TaskFlowService.openTaskDetails method.
    async open_task_details(args: any) {
      return service.openTaskDetails(String(args.taskId));
    },
  • JSON Schema for input validation of the open_task_details tool, defining the required 'taskId' parameter.
    open_task_details: {
      type: "object",
      properties: { taskId: { type: "string" } },
      required: ["taskId"],
    },
  • Tool object registration/definition exported from TaskFlowTools.ts, including name, description, and input schema. This object is imported and registered in the MCP server.
    export const OPEN_TASK_DETAILS_TOOL: Tool = {
      name: "open_task_details",
      description:
        "Get details of a specific task by 'taskId'. This is for inspecting task information at any point.",
      inputSchema: {
        type: "object",
        properties: {
          taskId: { type: "string" },
        },
        required: ["taskId"],
      },
    };
  • Registration of the OPEN_TASK_DETAILS_TOOL in the MCP server's listTools response, making it available to clients.
    OPEN_TASK_DETAILS_TOOL,
  • Core helper method in TaskFlowService that implements the business logic: loads tasks, searches for the task by ID across all requests, enhances description with prompts, and returns full task details.
    public async openTaskDetails(taskId: string) {
      await this.loadTasks();
      
      // Find the task across all requests
      for (const req of this.data.requests) {
        const task = req.tasks.find((t) => t.id === taskId);
        if (task) {
          const enhancedDescription = this.applyPromptsToTaskDescription(task.description, this.data.prompts);
          return {
            status: "task_found",
            task: {
              id: task.id,
              title: task.title,
              description: enhancedDescription,
              done: task.done,
              completedDetails: task.completedDetails,
              subtasks: task.subtasks,
              dependencies: task.dependencies || [],
              ...(this.data.prompts?.instructions && { instructions: this.data.prompts.instructions })
            },
            requestId: req.requestId,
            message: "Task details retrieved successfully."
          };
        }
      }
      
      return { status: "error", message: "Task not found" };
    }
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 of behavioral disclosure. It states the tool is for 'inspecting' information, implying a read-only operation, but does not clarify if it requires authentication, has rate limits, returns specific data formats, or handles errors. For a tool with zero annotation coverage, this is a significant gap in transparency.

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 front-loaded, consisting of two clear sentences: the first states the core functionality, and the second adds contextual usage. There is no redundant or verbose language, making it efficient and easy to parse.

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 the complexity of task management tools, no annotations, no output schema, and incomplete parameter documentation (0% schema coverage), the description is insufficient. It does not explain what details are returned, error conditions, or how it fits into broader workflows with siblings like 'update_task'. More context is needed for effective use.

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 description adds meaning by specifying that 'taskId' is used to get details of a specific task, which clarifies the parameter's role beyond the schema's basic type definition. However, with 0% schema description coverage and only one parameter, the description does not fully compensate by explaining the format or constraints of 'taskId' (e.g., expected string pattern). The baseline is appropriate given the minimal parameter count.

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: 'Get details of a specific task by 'taskId''. It specifies the verb ('Get details'), resource ('task'), and key identifier ('taskId'), making the action explicit. However, it does not differentiate from sibling tools like 'get_next_task' or 'list_requests', which also retrieve task-related information, so it falls short of 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 provides implied usage context with 'This is for inspecting task information at any point', suggesting it can be used flexibly. However, it lacks explicit guidance on when to use this tool versus alternatives like 'get_next_task' or 'list_requests', and does not mention prerequisites or exclusions. This leaves room for ambiguity in tool selection.

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

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/pinkpixel-dev/taskflow-mcp'

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