Skip to main content
Glama

ask-kimi

Destructive

Send coding tasks or questions to Kimi Code CLI with file analysis and session support. Resolve problems via natural language, including file references and safety controls.

Instructions

Execute Kimi Code CLI with file analysis (@syntax), session resume, MCP passthrough, and safety controls.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cdNoWorking directory
afkNo--afk: auto-approve in away-from-keyboard mode (print mode implies this).
planNoStart in plan mode (--plan). For richer planning, prefer the plan-kimi tool.
yoloNo⚠️ --yolo: auto-approve everything (dangerous, full file access).
agentNoBuiltin agent spec to use (--agent). "default" or "okabe".
modelNoOptional model override. Known: kimi-for-coding, kimi-k2-6, kimi-k2-6-turbo, kimi-k2-thinking-turbo, kimi-k2-5, kimi-latest. If omitted, uses your Kimi CLI default (~/.kimi/config.toml).
quietNoUse --quiet (= --print --output-format text --final-message-only).
configNoConfiguration overrides — string (JSON/TOML) or object passed via --config.
dryRunNoReturn the resolved CLI argv as JSON without spawning Kimi.
promptYesTask or question. Use @ to include files (e.g., '@largefile.ts explain').
addDirsNoAdditional writable directories (--add-dir, repeatable).
timeoutNoMaximum execution time in milliseconds (optional)
thinkingNoToggle thinking mode (overrides default_thinking from config).
agentFileNoCustom agent spec file (--agent-file).
finalOnlyNoAdd --final-message-only — skip intermediate tool-call output. Default: true.
sessionIdNoInternal session ID for conversation continuity (workspace-isolated).
configFileNoPath to a config file (TOML or JSON).
skillsDirsNoCustom skills directories (--skills-dir, repeatable). Overrides default discovery.
workingDirNoWorking directory for execution (alias of cd)
outputFormatNoKimi --output-format. "text" (default for clean responses) or "stream-json" (JSONL with assistant + tool messages).
resetSessionNoClear session context before execution. Starts fresh conversation.
responseModeNoResponse verbosity: "clean" returns only the final answer (default), "full" includes tool calls and stderr execution log.clean
mcpConfigFileNoPath to an MCP config file with `mcpServers` (passed via --mcp-config-file).
continueLatestNoUse --continue to resume the most recent Kimi session in cwd.
includeMetadataNoInclude tool-call metadata in response (only meaningful with stream-json).
maxStepsPerTurnNoCap steps in one turn (--max-steps-per-turn).
maxRalphIterationsNoExtra autonomous iterations after the first turn (--max-ralph-iterations, -1 = unlimited).
Behavior3/5

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

Annotations already indicate destructiveHint and openWorldHint. The description adds context about safety controls but does not elaborate on destructive behaviors or side effects. It partially compensates by mentioning session resume and MCP passthrough.

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 a single sentence that efficiently lists key features without verbosity. It is front-loaded with the primary action, though the comma-separated list could be more structured for clarity.

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 complexity (27 parameters) and absence of output schema, the description is too brief. It does not describe return values or expected output format, leaving gaps for an agent to fully understand the tool's behavior.

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?

Schema coverage is 100%, so baseline is 3. The description adds value by summarizing key parameter intents (e.g., '@syntax' for prompt, session resume for sessionId, MCP passthrough for mcpConfigFile), helping the agent understand high-level functionality beyond individual schema descriptions.

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 executes the Kimi Code CLI, specifying key features like file analysis, session resume, MCP passthrough, and safety controls. However, it does not explicitly differentiate from sibling tools such as plan-kimi or brainstorm, which may have overlapping capabilities.

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 like plan-kimi or brainstorm. Given the many sibling tools, explicit usage context is missing.

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/x51xxx/kimi-mcp-server'

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