Skip to main content
Glama

kiro_session_list

View active Kiro CLI sessions to manage multiple project workflows and monitor running processes for better orchestration.

Instructions

List all active kiro-cli sessions

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The primary handler function for the kiro_session_list tool. It lists all active sessions using SessionManager.list_sessions(), formats them into a dictionary with sessions list, active session ID, and count.
    async def _handle_session_list(session_manager: SessionManager) -> dict[str, Any]:
        """Handle kiro_session_list tool call."""
        sessions = await session_manager.list_sessions()
        return {
            "sessions": [s.to_info().to_dict() for s in sessions],
            "active_session_id": session_manager.active_session_id,
            "count": len(sessions),
        }
  • Tool schema definition in the TOOLS list, including name, description, and empty inputSchema (no parameters required).
    {
        "name": "kiro_session_list",
        "description": "List all active kiro-cli sessions",
        "inputSchema": {
            "type": "object",
            "properties": {}
        }
    },
  • MCP tool registration via the list_tools handler, which loads all tool definitions from tools.py (including kiro_session_list) and returns them as Tool objects.
    @server.list_tools()
    async def handle_list_tools() -> list[Tool]:
        """List available tools."""
        tools_data = get_all_tools()
        return [
            Tool(
                name=tool["name"],
                description=tool["description"],
                inputSchema=tool["inputSchema"]
            )
            for tool in tools_data
        ]
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 the tool lists active sessions but doesn't describe what constitutes an 'active' session, how the list is formatted, whether it includes metadata, or if there are limitations like pagination or rate constraints. This leaves significant gaps in understanding the tool's behavior.

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, clear sentence with no wasted words. It's front-loaded with the core purpose ('List all active kiro-cli sessions'), making it highly efficient and easy to parse, which is ideal for a tool with no parameters.

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's low complexity (0 parameters, no output schema, no annotations), the description is minimally adequate. It states what the tool does but lacks details on behavior, output format, or usage context. Without annotations or output schema, more context on what 'active' means or the list structure would improve completeness, but it meets the basic threshold for a simple list tool.

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 0 parameters, and schema description coverage is 100%, so there are no parameters to document. The description doesn't need to add parameter semantics, and it correctly avoids mentioning any inputs, aligning with the empty schema. A baseline of 4 is appropriate as no compensation is needed for missing parameter info.

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 ('List') and resource ('all active kiro-cli sessions'), providing a specific verb+resource combination. It distinguishes from some siblings like 'kiro_session_clear' or 'kiro_session_create' by focusing on listing rather than modifying sessions, though it doesn't explicitly differentiate from 'kiro_session_switch' or 'kiro_session_end' in terms of purpose.

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?

No guidance is provided on when to use this tool versus alternatives. It doesn't mention prerequisites, timing considerations, or how it differs from sibling tools like 'kiro_task_list' or 'kiro_agents_list', leaving the agent to infer usage context without explicit direction.

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