Skip to main content
Glama
brysontang

DeltaTask MCP Server

by brysontang

create_subtasks

Break down complex tasks into manageable subtasks with categories to organize work and track progress in your task management system.

Instructions

Create multiple subtasks for a parent task with categories.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
task_idYes
subtasksYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • server.py:77-80 (handler)
    MCP tool handler function for 'create_subtasks', registered via @mcp.tool() decorator. Delegates to TaskService.create_subtasks.
    @mcp.tool()
    async def create_subtasks(task_id: str, subtasks: list[dict[str, Any]]) -> dict[str, Any]:
        """Create multiple subtasks for a parent task with categories."""
        return service.create_subtasks(task_id, subtasks)
  • Core implementation of create_subtasks in TaskService class. Validates parent task, sets parent_id on each subtask, calls add_task to create them, and returns subtask IDs.
    def create_subtasks(self, task_id: str, 
                      subtasks: List[Dict[str, Any]]) -> Dict[str, Any]:
        """Create subtasks for a task and return their IDs."""
        # Check if parent task exists
        parent_task = self.repository.get_todo_by_id(task_id)
        if not parent_task:
            return {"error": "Parent task not found"}
        
        subtask_ids = []
        
        # Create each subtask
        for subtask in subtasks:
            subtask['parent_id'] = task_id
            subtask_id = self._ensure_id(subtask)
            self.add_task(subtask)
            subtask_ids.append(subtask_id)
        
        return {
            "message": f"Created {len(subtask_ids)} subtasks",
            "subtask_ids": subtask_ids
        }
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. While 'Create' implies a write operation, it doesn't specify permissions required, whether changes are reversible, rate limits, or what happens if the parent task doesn't exist. The mention of 'categories' hints at additional behavior but is vague, leaving significant gaps in understanding how the tool behaves.

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 that gets straight to the point without unnecessary words. It's front-loaded with the core action, though the trailing phrase 'with categories' feels slightly tacked on. Overall, it's concise and well-structured for its length.

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 has an output schema (which reduces the need to describe return values) but no annotations and 0% schema coverage, the description is minimally adequate. It covers the basic purpose but lacks details on usage, parameters, and behavioral traits, making it incomplete for a mutation tool with undocumented parameters.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the schema provides no parameter details. The description mentions 'categories' but doesn't explain how this relates to the 'subtasks' array parameter or what 'task_id' should be. It adds minimal meaning beyond the bare parameter names, failing to compensate for the lack of schema documentation.

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 action ('Create multiple subtasks') and the target resource ('for a parent task'), which is specific and actionable. However, it doesn't explicitly distinguish this tool from sibling tools like 'create_task' or 'update_task', which prevents a perfect score. The mention of 'categories' adds some specificity but isn't fully explained.

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 'create_task' or 'update_task'. It doesn't mention prerequisites (e.g., needing an existing parent task) or exclusions (e.g., not for single subtasks). Without such context, an AI agent might struggle to select this tool appropriately among siblings.

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/brysontang/DeltaTask'

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