Skip to main content
Glama

open_task_details

Retrieve detailed information about a specific task using its taskId to inspect status, progress, and execution data within the 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 core handler function that implements the logic for the 'open_task_details' tool. It searches all requests for the task by ID and returns formatted details including ID, title, description, status, and completion details if available.
      public async openTaskDetails(taskId: string) {
        for (const request of this.data.requests) {
          const task = request.tasks.find((t) => t.id === taskId);
          if (task) {
            return {
              message: `Task Details:
    ID: ${task.id}
    Title: ${task.title}
    Description: ${task.description}
    Status: ${task.approved ? "Approved" : task.done ? "Done" : "Pending"}
    ${
      task.completedDetails
        ? `Completion Details: ${task.completedDetails}`
        : ""
    }`,
            };
          }
        }
        throw new Error("Task not found");
      }
  • Zod schema defining the input parameters for the 'open_task_details' tool, which requires a 'taskId' string.
    const OpenTaskDetailsSchema = z.object({
      taskId: z.string(),
    });
  • index.ts:170-174 (registration)
    Tool registration in the listTools() method, defining the name, description, and input schema for 'open_task_details'.
    {
      name: "open_task_details",
      description: "Get details of a specific task.",
      inputSchema: OpenTaskDetailsSchema,
    },
  • index.ts:247-253 (registration)
    Dispatcher case in callTool() method that validates input using the schema and delegates to the openTaskDetails handler.
    case "open_task_details": {
      const parsed = OpenTaskDetailsSchema.safeParse(parameters);
      if (!parsed.success) {
        throw new Error(`Invalid parameters: ${parsed.error}`);
      }
      return this.openTaskDetails(parsed.data.taskId);
    }
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 this is for 'inspecting' (implying read-only) but doesn't clarify permissions, rate limits, or what 'details' include. For a tool with zero annotation coverage, this leaves significant gaps in understanding its 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 two concise sentences with zero waste. It front-loads the core purpose and adds a brief usage note, making it efficiently structured and easy to parse.

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 no annotations, no output schema, and low schema coverage, the description is incomplete. It covers the basic purpose but lacks details on return values, error conditions, or behavioral traits. For a simple read tool, it's minimally adequate but has clear gaps.

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 schema description coverage is 0%, but the description adds meaning by specifying that 'taskId' identifies the task to get details for. However, it doesn't explain the format or constraints of 'taskId' beyond what the schema's type indicates. With one parameter, the baseline is 4, but the minimal added value reduces it to 3.

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 verb ('Get details') and resource ('specific task by taskId'), making the purpose unambiguous. However, it doesn't explicitly differentiate from sibling tools like 'get_next_task' or 'list_requests', which might also retrieve task information in different contexts.

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 ('for inspecting task information at any point') but doesn't specify when to use this versus alternatives like 'get_next_task' or 'list_requests'. It provides some context but lacks explicit guidance on exclusions or prerequisites.

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/Rudra-ravi/mcp-taskmanager'

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