Skip to main content
Glama
blizzy78

Task Manager MCP Server

by blizzy78

Get task info

task_info

Retrieve detailed information for specific tasks by providing their IDs, enabling status tracking and management within the Task Manager MCP Server.

Instructions

Returns full details for requested tasks

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
taskIDsYesA list of task IDs to retrieve information for

Implementation Reference

  • The main execution logic for the 'task_info' tool: retrieves tasks by IDs from taskDB, collects not found IDs, computes incomplete tasks in tree if applicable, returns structured content.
    export async function handleTaskInfo({ taskIDs }: TaskInfoArgs, taskDB: TaskDB, singleAgent: boolean) {
      const tasks = new Array<Task>()
      const notFoundTaskIDs = new Array<TaskID>()
    
      for (const taskID of taskIDs) {
        const task = taskDB.get(taskID)
        if (!task) {
          notFoundTaskIDs.push(taskID)
          continue
        }
    
        tasks.push(task)
      }
    
      const incompleteTaskIDs =
        notFoundTaskIDs.length === 0 ? taskDB.incompleteTasksInTree(taskIDs[0]).map((t) => t.taskID) : undefined
    
      const res = {
        tasks,
        notFoundTasks: notFoundTaskIDs,
        incompleteTasksIdealOrder: singleAgent ? incompleteTaskIDs : undefined,
      }
    
      return {
        content: [],
        structuredContent: res,
      } satisfies CallToolResult
    }
  • Zod input schema for the task_info tool, requiring a non-empty array of task IDs.
    export const TaskInfoArgsSchema = z.object({
      taskIDs: TaskIDSchema.array().min(1).describe('A list of task IDs to retrieve information for'),
    })
  • tools/index.ts:39-42 (registration)
    Maps the TASK_INFO name to its handler and schema in the central toolHandlers() function, used for dispatching tool calls.
    [TASK_INFO]: {
      handler: handleTaskInfo,
      schema: TaskInfoArgsSchema,
    } satisfies ToolHandlerInfo,
  • Tool metadata definition (name, title, description, inputSchema) included in the tools() array for MCP tool exposure.
    export const taskInfoTool = {
      name: TASK_INFO,
      title: 'Get task info',
      description: 'Returns full details for requested tasks',
      inputSchema: zodToJsonSchema(TaskInfoArgsSchema, { $refStrategy: 'none' }),
    }
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 a read operation ('Returns'), which is helpful, but doesn't cover aspects like whether it requires authentication, rate limits, error handling, or what 'full details' includes (e.g., format, fields). This leaves significant gaps for a tool with no annotation coverage.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence with no wasted words, making it easy to parse. However, it could be more front-loaded with key distinctions from siblings to improve structure, but it's appropriately sized for its purpose.

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 a read operation with no annotations and no output schema, the description is incomplete. It doesn't explain what 'full details' means in terms of return values, error cases, or behavioral traits, leaving the agent with insufficient context to use the tool effectively beyond basic parameter input.

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 100%, with the parameter 'taskIDs' well-documented in the schema as 'A list of task IDs to retrieve information for'. The description adds no additional meaning beyond this, such as ID format examples or constraints, so it meets the baseline for high schema coverage without compensating value.

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 'Returns full details for requested tasks' clearly states the verb ('Returns') and resource ('full details for requested tasks'), but it's somewhat vague about what 'full details' entails and doesn't differentiate from sibling tools like 'current_task' or 'decompose_task'. It's better than a tautology but lacks specificity about what makes this tool distinct.

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 'current_task' (which might get current task info) or 'decompose_task' (which might break down tasks). There's no mention of prerequisites, context, or exclusions, leaving the agent to infer usage from the tool name alone.

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/blizzy78/mcp-task-manager'

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