Skip to main content
Glama

kiro_task_list

List and manage active asynchronous tasks in Kiro CLI MCP Server, with options to filter by session ID and include completed tasks for comprehensive workflow oversight.

Instructions

List active async tasks

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
session_idNoOptional filter by session ID
include_doneNoInclude completed/failed tasks

Implementation Reference

  • Handler function that implements the core logic of kiro_task_list by parsing arguments and delegating to StreamingTaskManager.list_tasks to retrieve and format the list of active tasks.
    async def _handle_task_list(
        task_manager: StreamingTaskManager,
        arguments: dict[str, Any]
    ) -> dict[str, Any]:
        """Handle kiro_task_list tool call - list active tasks."""
        session_id = arguments.get("session_id")
        include_done = arguments.get("include_done", False)
        
        tasks = await task_manager.list_tasks(session_id, include_done)
        
        return {
            "tasks": [t.to_dict() for t in tasks],
            "count": len(tasks),
        }
  • Schema definition for the kiro_task_list tool, specifying input parameters: optional session_id (string) and include_done (boolean, default False). This is part of the TOOLS list used for MCP tool registration.
    {
        "name": "kiro_task_list",
        "description": "List active async tasks",
        "inputSchema": {
            "type": "object",
            "properties": {
                "session_id": {
                    "type": "string",
                    "description": "Optional filter by session ID"
                },
                "include_done": {
                    "type": "boolean",
                    "description": "Include completed/failed tasks",
                    "default": False
                }
            }
        }
    },
  • Registration/dispatch point in the main handle_call_tool function where kiro_task_list calls are routed to the specific handler.
    elif name == "kiro_task_list":
        result = await _handle_task_list(task_manager, arguments)
Behavior2/5

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

No annotations are provided, so the description carries full burden. 'List active async tasks' implies a read-only operation but doesn't disclose behavioral traits like whether it's safe, if it requires authentication, rate limits, or what 'active' means (e.g., pending vs. running). This is inadequate 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.

Conciseness5/5

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

The description is a single, efficient phrase ('List active async tasks') that is front-loaded and wastes no words. Every element contributes directly to understanding the tool's purpose, making it highly concise and well-structured.

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 no annotations and no output schema, the description is incomplete. It doesn't explain what 'active' entails, how tasks are returned (e.g., format, pagination), or error handling. For a tool with siblings and potential complexity, this leaves significant gaps for an AI agent.

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 description adds no parameter semantics beyond what's in the input schema, which has 100% coverage. It doesn't explain the meaning of 'active' in relation to 'include_done' or provide usage examples. With high schema coverage, the baseline is 3, as the schema already documents parameters adequately.

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 'List active async tasks' clearly states the verb ('List') and resource ('active async tasks'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'kiro_task_status' or 'kiro_task_cancel', 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. With siblings like 'kiro_task_status' and 'kiro_task_cancel' available, there's no indication of whether this is for bulk listing versus specific task operations, leaving the agent without context for selection.

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/vanphappi/kiro-cli-mcp'

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