Skip to main content
Glama

getExecutableTaskList

Retrieve pending tasks with all dependencies satisfied to identify immediate next actions in AI agent task management.

Instructions

获取当前所有依赖已满足且状态为 'pending' 的可执行任务列表。

Returns: ToolResponse[List[TaskOutput]]: 包含可执行任务列表的响应对象。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The MCP tool handler for 'getExecutableTaskList', decorated with @mcp.tool() which registers the tool and defines its interface. It delegates execution to the PlanManager instance.
    @mcp.tool()
    def getExecutableTaskList() -> ToolResponse[List[TaskOutput]]:
        """
        获取当前所有依赖已满足且状态为 'pending' 的可执行任务列表。
    
        Returns:
            ToolResponse[List[TaskOutput]]: 包含可执行任务列表的响应对象。
        """
        return plan_manager.getExecutableTaskList()
  • Core implementation logic in PlanManager class that computes the list of executable tasks by filtering pending tasks with all dependencies satisfied.
    def getExecutableTaskList(self) -> Dict:
        """获取所有可执行的任务列表"""
        executable_tasks = []
        for task in self.plan_data["tasks"]:
            if task["status"] == "pending" and self._check_dependencies_satisfied(task):
                executable_tasks.append(task)
        
        return {"success": True, "data": executable_tasks}
  • Pydantic model defining the structure of individual TaskOutput objects returned in the tool's List[TaskOutput] response.
    class TaskOutput(BaseModel):
        """
        用于工具函数返回任务信息时,定义单个任务输出的Pydantic模型。
        """
        id: int
        name: str
        status: str
        dependencies: List[int]
        reasoning: str
        result: Optional[str] = None
  • Generic Pydantic model wrapping the tool response, used as ToolResponse[List[TaskOutput]] for input/output schema.
    class ToolResponse(BaseModel, Generic[T]):
        """
        一个通用的工具响应模型,用于标准化所有工具的返回结构。
        """
        success: bool = Field(True, description="操作是否成功。")
        message: Optional[str] = Field(None, description="关于操作结果的可读消息。")
        data: Optional[T] = Field(None, description="操作返回的主要数据负载。")
  • Instantiation of the PlanManager instance used by the tool handler. (Note: Registration is via @mcp.tool() decorator on the handler.)
    plan_manager = PlanManager()
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 it describes what the tool returns (a list of executable pending tasks), it doesn't address important behavioral aspects like whether this is a read-only operation, potential side effects, authentication requirements, rate limits, or error conditions. The description is minimal and lacks the depth needed for a mutation-free tool with zero 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 appropriately concise with two sentences: one stating the purpose and one describing the return type. Both sentences earn their place by providing essential information. It's front-loaded with the core functionality. Minor improvement could be made by integrating the return information more seamlessly, but overall it's efficient.

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 zero parameters, no annotations, and no output schema, the description provides adequate basic information about what the tool does and what it returns. However, it lacks important context about behavioral traits (safety, side effects) and doesn't help differentiate from sibling tools in a crowded task management domain. The description meets minimum requirements but leaves gaps in usage guidance and behavioral transparency.

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

Parameters4/5

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

The tool has zero parameters, and schema description coverage is 100% (empty schema). The description appropriately doesn't waste space discussing non-existent parameters. It focuses on the tool's purpose and return value, which is the correct approach for a parameterless tool. A perfect score isn't given because the description could theoretically mention why there are no parameters, but this is minor.

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 tool's purpose: '获取当前所有依赖已满足且状态为 'pending' 的可执行任务列表' (Get a list of all currently executable tasks with dependencies satisfied and status 'pending'). It specifies the verb ('获取' - get) and resource ('可执行任务列表' - executable task list) with filtering criteria. However, it doesn't explicitly differentiate from sibling tools like 'getTaskList' or 'getCurrentTask', which prevents a perfect score.

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. There are multiple sibling tools related to tasks (getTaskList, getCurrentTask, getPlanStatus) with overlapping domains, but the description doesn't indicate when this specific filtered list is appropriate versus other task retrieval tools. No exclusions or prerequisites are mentioned.

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