Skip to main content
Glama

kiro_agents_list

List available custom agents in the Kiro CLI MCP Server to manage and select agents for session orchestration and workflow support.

Instructions

List available custom agents

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The core handler function for the kiro_agents_list tool. It asynchronously lists available agents using the CommandExecutor and returns them as a JSON-serializable dictionary with agents list and count.
    async def _handle_agents_list(command_executor: CommandExecutor) -> dict[str, Any]:
        """Handle kiro_agents_list tool call."""
        agents = await command_executor.list_agents()
        return {
            "agents": [a.to_dict() for a in agents],
            "count": len(agents),
        }
  • The JSON schema definition for the kiro_agents_list tool, specifying its name, description, and empty input schema (no required parameters). This is included in the TOOLS list used for tool registration.
    {
        "name": "kiro_agents_list",
        "description": "List available custom agents",
        "inputSchema": {
            "type": "object",
            "properties": {}
        }
    },
  • Dispatch/registration logic in the main @server.call_tool() handler. Routes calls to 'kiro_agents_list' to the dedicated _handle_agents_list function.
    elif name == "kiro_agents_list":
        result = await _handle_agents_list(command_executor)
  • The @server.list_tools() handler that registers all tools, including kiro_agents_list, by calling get_all_tools() from tools.py and converting to MCP 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?

No annotations are provided, so the description carries the full burden of behavioral disclosure. While 'List' implies a read-only operation, the description doesn't specify what 'available' means (e.g., active vs. all, filtered by permissions), whether results are paginated, what format they return, or any rate limits. For a tool with zero annotation coverage, this leaves significant behavioral questions unanswered.

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 zero wasted words. It's front-loaded with the essential information ('List available custom agents') and doesn't include any unnecessary elaboration. This is an excellent example of concise, effective documentation for a simple tool.

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 zero-parameter list tool with no output schema, the description provides the minimum viable information about what it does. However, without annotations or output schema, it doesn't address what the return format looks like (e.g., array of agent objects with what properties) or behavioral constraints. It's adequate but leaves gaps that would help an agent use it effectively.

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% (though empty). The description appropriately doesn't discuss parameters since none exist. It correctly focuses on the tool's purpose rather than trying to document non-existent inputs, earning a high score for parameter relevance.

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 the resource ('available custom agents'), making the purpose immediately understandable. It doesn't explicitly distinguish from siblings like 'kiro_session_list' or 'kiro_task_list', but the specificity of 'custom agents' provides some differentiation. This is a clear, functional description that tells the agent exactly what to expect.

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_session_list' and 'kiro_task_list' that also list resources, there's no indication of when 'custom agents' listing is appropriate versus session or task listing. No prerequisites, exclusions, or alternative tools 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/vanphappi/kiro-cli-mcp'

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