Skip to main content
Glama

skipTask

Mark tasks as skipped in MCPlanManager to resolve dependencies and allow subsequent tasks to proceed. Specify a task ID and reason for skipping.

Instructions

将指定ID的任务标记为 'skipped' (已跳过)。 被跳过的任务在依赖解析中被视为“已完成”,允许后续任务继续。

Args: task_id (int): 需要跳过的任务的ID (从0开始)。 reason (str): 解释为何跳过此任务的字符串。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
task_idYes
reasonYes

Implementation Reference

  • MCP tool handler and registration for skipTask. This thin wrapper delegates to PlanManager.skipTask for the core logic.
    @mcp.tool()
    def skipTask(task_id: int, reason: str) -> ToolResponse[TaskOutput]:
        """
        将指定ID的任务标记为 'skipped' (已跳过)。
        被跳过的任务在依赖解析中被视为“已完成”,允许后续任务继续。
    
        Args:
            task_id (int): 需要跳过的任务的ID (从0开始)。
            reason (str): 解释为何跳过此任务的字符串。
        """
        return plan_manager.skipTask(task_id, reason)
  • Core implementation of skipTask logic in PlanManager class. Finds the task, validates status, marks it as skipped, updates result and timestamp.
    def skipTask(self, task_id: int, reason: str) -> Dict:
        """跳过任务"""
        task = self._find_task_by_id(task_id)
        if not task:
            return {"success": False, "message": f"Task {task_id} not found"}
        
        if task["status"] not in ["pending", "failed"]:
             return {"success": False, "message": f"Only pending or failed tasks can be skipped. Task {task_id} has status '{task['status']}'"}
        
        task["status"] = "skipped"
        task["result"] = f"Skipped: {reason}"
        
        self._update_timestamp()
        
        return {
            "success": True,
            "data": task,
            "message": f"Task {task_id} skipped. Reason: {reason}"
        }
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries full burden. It discloses key behavioral traits: the skipped status affects dependency resolution (treating skipped tasks as 'completed'), which is crucial context. However, it doesn't mention permissions needed, whether the action is reversible, or what happens if the task_id doesn't exist.

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 perfectly structured with a clear purpose statement followed by a well-organized parameter section. Every sentence earns its place, with no wasted words. The bilingual format (Chinese with English parameter names) is efficient and clear.

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?

For a mutation tool with no annotations and no output schema, the description provides adequate basics but lacks completeness. It explains what the tool does and its parameters well, but doesn't cover error conditions, return values, or system state changes beyond the dependency resolution effect mentioned.

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

Parameters5/5

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

With 0% schema description coverage, the description fully compensates by explaining both parameters clearly. It specifies task_id is an integer starting from 0, and reason is a string explaining why the task is skipped. This adds essential meaning beyond the bare schema.

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

Purpose5/5

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

The description clearly states the specific action ('标记为 skipped' - mark as skipped) on a specific resource ('指定ID的任务' - task with specified ID). It distinguishes from siblings like completeTask and failTask by specifying the unique 'skipped' status and its effect on dependency resolution.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear context about when to use this tool: when a task needs to be marked as skipped to allow dependent tasks to proceed. It doesn't explicitly state when NOT to use it or name specific alternatives, but the context is sufficient for understanding its role among sibling tools like completeTask and failTask.

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/donway19/MCPlanManager'

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