Skip to main content
Glama

kiro_command

Execute kiro-cli commands to manage sessions, pool processes for faster responses, and support multi-project workflows through isolated contexts.

Instructions

Execute a kiro-cli command (e.g., /mcp, /help)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
commandYesThe command to execute
session_idNoOptional session ID

Implementation Reference

  • The core handler function for the 'kiro_command' tool. It extracts the command and session_id from arguments, retrieves or creates the session, executes the command using CommandExecutor, and returns the result as a dictionary.
    async def _handle_command(
        session_manager: SessionManager,
        command_executor: CommandExecutor,
        arguments: dict[str, Any]
    ) -> dict[str, Any]:
        """Handle kiro_command tool call."""
        command = arguments.get("command", "")
        session_id = arguments.get("session_id")
    
        session = await session_manager.get_or_create_session(session_id)
        result = await command_executor.execute_command(session, command)
    
        return result.to_dict()
  • Input schema for the 'kiro_command' tool, defining the required 'command' parameter and optional 'session_id'.
    {
        "name": "kiro_command",
        "description": "Execute a kiro-cli command (e.g., /mcp, /help)",
        "inputSchema": {
            "type": "object",
            "properties": {
                "command": {
                    "type": "string",
                    "description": "The command to execute"
                },
                "session_id": {
                    "type": "string",
                    "description": "Optional session ID"
                }
            },
            "required": ["command"]
        }
  • Registration of tools via the MCP list_tools handler, which includes 'kiro_command' from the tools.py TOOLS list.
    @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
        ]
  • Dispatch routing in the main @server.call_tool() handler that directs 'kiro_command' calls to the specific _handle_command function.
    elif name == "kiro_command":
        result = await _handle_command(session_manager, command_executor, arguments)
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 executes commands but doesn't describe what that entails—whether it's read-only or mutative, what permissions are needed, how errors are handled, or what the output looks like. This is inadequate for a command execution 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.

Conciseness5/5

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

The description is extremely concise—a single sentence with parenthetical examples—and front-loaded with the core purpose. Every word earns its place, making it easy to parse without unnecessary elaboration.

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 the complexity of a command execution tool with no annotations, no output schema, and many siblings, the description is incomplete. It doesn't address behavioral traits, usage context, or output expectations, leaving significant gaps for the agent to navigate.

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 schema description coverage is 100%, so the schema already documents both parameters fully. The description adds no additional meaning beyond what's in the schema, such as command syntax examples or session ID context. Baseline 3 is appropriate when the schema does the heavy lifting.

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 verb 'execute' and the resource 'kiro-cli command', with examples like '/mcp' and '/help' that help illustrate the tool's function. However, it doesn't explicitly differentiate this general command execution tool from its more specific siblings like kiro_chat or kiro_task_list, which might handle particular command types.

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 its siblings. It doesn't mention alternatives, prerequisites, or exclusions, leaving the agent to infer usage from context alone. This is a significant gap given the many specialized sibling tools available.

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