Skip to main content
Glama

get_task_details

Retrieve execution details for a specific task by providing its unique ID. View task status, input/output data, and execution information to monitor and troubleshoot workflow performance.

Instructions

Get details of a specific task execution by task ID. Returns task status, input/output, and execution details.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
taskIdYesThe unique task execution ID

Implementation Reference

  • The handler function for the 'get_task_details' tool. It extracts the taskId from the input arguments, makes an API call to the Conductor server to retrieve task details from the `/tasks/{taskId}` endpoint, and returns the response data as a formatted JSON string in the tool response format.
    case "get_task_details": {
      const { taskId } = args as any;
      const response = await conductorClient.get(`/tasks/${taskId}`);
      
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(response.data, null, 2),
          },
        ],
      };
    }
  • The input schema definition for the 'get_task_details' tool, specifying that it requires a 'taskId' string parameter.
      inputSchema: {
        type: "object",
        properties: {
          taskId: {
            type: "string",
            description: "The unique task execution ID",
          },
        },
        required: ["taskId"],
      },
    },
  • src/index.ts:452-466 (registration)
    The tool registration object included in the 'tools' array, which is returned by the list_tools handler. This defines the tool's name, description, and input schema for discovery by MCP clients.
    {
      name: "get_task_details",
      description:
        "Get details of a specific task execution by task ID. Returns task status, input/output, and execution details.",
      inputSchema: {
        type: "object",
        properties: {
          taskId: {
            type: "string",
            description: "The unique task execution ID",
          },
        },
        required: ["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 the tool returns task status, input/output, and execution details, which is helpful. However, it lacks critical information such as whether this is a read-only operation (implied but not stated), error handling (e.g., for invalid task IDs), performance characteristics, or authentication needs. 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 extremely concise and front-loaded, consisting of two sentences that directly state the purpose and return values without any fluff. Every word earns its place, making it easy for an agent to parse quickly. This efficiency is exemplary for tool descriptions.

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 low complexity (single parameter, no nested objects) and 100% schema coverage, the description is minimally adequate. However, with no annotations and no output schema, it should ideally provide more behavioral context (e.g., read-only nature, error cases) to compensate. The description covers basic functionality but leaves gaps in operational understanding, making it just sufficient for simple use cases.

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 'taskId' well-documented as 'The unique task execution ID'. The description adds no additional parameter semantics beyond what the schema provides, such as format examples or constraints. Given the high schema coverage, a baseline score of 3 is appropriate, as the description doesn't compensate but also doesn't detract.

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 execution by task ID', making the purpose immediately understandable. It distinguishes from siblings like get_task_logs (logs) and get_workflow_status (workflow-level status), though not explicitly. However, it could be more specific about what distinguishes it from get_task_definition (definition vs. execution details).

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 like get_task_definition or get_task_logs. It mentions the task ID parameter but doesn't explain prerequisites (e.g., needing an existing task execution) or contextual usage (e.g., for monitoring or debugging). This leaves the agent without clear direction on selection among similar tools.

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/opensensor/conductor-mcp'

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