Skip to main content
Glama

get_task_details

Retrieve detailed information about a specific task, including its status and dependencies, to monitor progress and coordinate workflow execution.

Instructions

Get details of a specific task

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
task_idYesID of the task to get details for

Implementation Reference

  • The handler function for the 'get_task_details' tool. It extracts the task_id from arguments, retrieves the task from the tasks object, and returns its JSON details or throws an error if not found.
    case "get_task_details": {
      const { task_id } = request.params.arguments as { task_id: string };
      debug(`Getting details for task ${task_id}`);
    
      const task = tasks[task_id];
      if (!task) {
        throw new McpError(ErrorCode.InvalidRequest, `Task ${task_id} not found`);
      }
    
      return {
        content: [{
          type: "text",
          text: JSON.stringify(task, null, 2)
        }]
      };
    }
  • src/index.ts:447-460 (registration)
    Registration of the 'get_task_details' tool in the ListTools response, including its name, description, and input schema definition.
    {
      name: "get_task_details",
      description: "Get details of a specific task",
      inputSchema: {
        type: "object",
        properties: {
          task_id: {
            type: "string",
            description: "ID of the task to get details for"
          }
        },
        required: ["task_id"]
      }
    }
  • TypeScript interface defining the structure of a Task, which is used by the get_task_details handler to type-check and serialize the returned task data.
    interface Task {
      id: string;
      description: string;
      status: 'pending' | 'in_progress' | 'completed';
      assignedTo?: string;
      result?: string;
      dependencies?: string[];
    }
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 this is a 'Get' operation, implying it's likely read-only, but doesn't confirm this or describe any other traits like authentication needs, rate limits, error conditions, or what 'details' encompass (e.g., full metadata vs. limited fields). 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 a single, clear sentence with zero waste: 'Get details of a specific task'. It's appropriately sized and front-loaded, directly stating the tool's purpose without unnecessary elaboration. Every word earns its place, making it highly concise and well-structured.

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 (a read operation with one parameter) and the absence of annotations and output schema, the description is incomplete. It doesn't explain what 'details' include, potential return values, or behavioral aspects like idempotency. For a tool in a set with multiple task-related siblings, more context is needed to distinguish it and guide proper 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 input schema has 100% description coverage, with the single parameter 'task_id' documented as 'ID of the task to get details for'. The description adds no additional meaning beyond this, such as format examples or constraints. With high schema coverage, the baseline score of 3 is appropriate, as the schema does the heavy lifting for parameter documentation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Get details of a specific task' clearly states the verb ('Get details') and resource ('a specific task'), making the purpose understandable. However, it doesn't differentiate this from sibling tools like 'get_task_status' or 'get_next_task', which likely also retrieve task information but with different scopes or filters. The description is adequate but lacks sibling distinction.

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. With siblings like 'get_task_status' (which might return only status info) and 'get_next_task' (which might retrieve the next pending task), there's no indication that this tool is for retrieving comprehensive details of a specified task ID. Usage is implied by the name but not explicitly stated in the description.

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/mokafari/orchestrator-server'

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