kimi-swarm-bridge

Delegate Kimi Task and Wait

kimi_delegate_and_wait

Destructive

Execute a delegated Kimi task, wait for completion, and return handoff and review data in one call. Supports swarm-mode evidence with worker and coordinator details when available.

Instructions

Start a Kimi task, wait for completion or another wait/terminal state, and return handoff and review data in one call. Prefer this for normal delegated work; use kimi_delegate_task when the caller needs immediate asynchronous control. The task may run commands and modify files. With swarmMode=true, structured swarmEvidence reports observed native AgentSwarm calls, worker counts, and coordinator/worker model-provider bindings when Kimi wire evidence is available.

Input Schema

TableJSON Schema

Name	Required	Description
`cwd`	Yes	Working directory visible to the Kimi runtime. In the managed hosted deployment use /workspace; local desktop paths are not automatically available to the remote runtime.
`plan`	Yes	Ordered implementation or analysis steps Kimi should follow. For swarm work, use distinct non-conflicting scopes that can be delegated to workers.
`task`	Yes	Concrete objective for Kimi to execute. Include the requested outcome and relevant constraints.
`model`	No	Configured Kimi model alias. In the managed ai& deployment omit this field to use the centrally configured model binding; do not pass a raw provider model ID unless Kimi exposes it as an alias.
`dedupe`	No	Optional duplicate-session guard. When supplied, the bridge searches recent sessions before creating a new session and may reuse a compatible match.
`thinking`	No	Optional Kimi thinking setting. Omit to use the bridge default; the managed pilot is configured for high thinking.
`sessionId`	No	Existing Kimi session ID to submit into. Omit for a fresh session; fresh sessions are recommended for new swarm jobs.
`swarmMode`	No	Set true to activate and verify Kimi native swarm mode before prompt submission. When true, the result includes structured swarmEvidence when Kimi wire records are available.
`timeoutMs`	No	Maximum time in milliseconds to wait for this call. A timeout returns control without aborting the Kimi session, so the same session can be waited on later.
`acceptanceCriteria`	Yes	Verifiable conditions that define successful completion. Pass an empty array only when there are genuinely no explicit acceptance checks.

Schema Changelog

Changes observed during successful MCP inspections.

Changed18 schema fields changedv0.3.2Sep 13, 2026

addedInput schema / properties / acceptanceCriteria / description

Added value: +"Verifiable conditions that define successful completion. Pass an empty array only when there are genuinely no explicit acceptance checks."

addedInput schema / properties / cwd / description

Added value: +"Working directory visible to the Kimi runtime. In the managed hosted deployment use /workspace; local desktop paths are not automatically available to the remote runtime."

addedInput schema / properties / dedupe / description

Added value: +"Optional duplicate-session guard. When supplied, the bridge searches recent sessions before creating a new session and may reuse a compatible match."

addedInput schema / properties / dedupe / properties / excludeEmpty / description

Added value: +"Whether sessions with no messages should be excluded from the dedupe search."

addedInput schema / properties / dedupe / properties / includeArchive / description

Added value: +"Whether archived sessions should be included in the dedupe search."

addedInput schema / properties / dedupe / properties / includeSummary / description

Added value: +"Fetch recent user/assistant summary data for candidate sessions. Adds latency; leave false for normal dedupe checks."

addedInput schema / properties / dedupe / properties / matchAnyCwd / description

Added value: +"Set true only when intentionally allowing reuse from a different working directory. Defaults to false for workspace safety."

addedInput schema / properties / dedupe / properties / pageSize / description

Added value: +"Maximum number of recent sessions to inspect for a title match. Defaults to 20."

addedInput schema / properties / dedupe / properties / reuseIfStatus / description

Added value: +"Statuses the caller permits for reuse. The bridge still only auto-reuses running, idle, awaiting_approval, and awaiting_question sessions."

addedInput schema / properties / dedupe / properties / status / description

Added value: +"Optional exact Kimi session-status filter, such as running, idle, awaiting_approval, awaiting_question, aborted, or failed."

addedInput schema / properties / dedupe / properties / titleContains / description

Added value: +"Case-insensitive substring used to find an existing recent session before creating a new one. Use a task-specific title fragment."

addedInput schema / properties / model / description

Added value: +"Configured Kimi model alias. In the managed ai& deployment omit this field to use the centrally configured model binding; do not pass a raw provider model ID unless Kimi exposes it as an alias."

addedInput schema / properties / plan / description

Added value: +"Ordered implementation or analysis steps Kimi should follow. For swarm work, use distinct non-conflicting scopes that can be delegated to workers."

addedInput schema / properties / sessionId / description

Added value: +"Existing Kimi session ID to submit into. Omit for a fresh session; fresh sessions are recommended for new swarm jobs."

addedInput schema / properties / swarmMode / description

Added value: +"Set true to activate and verify Kimi native swarm mode before prompt submission. When true, the result includes structured swarmEvidence when Kimi wire records are available."

addedInput schema / properties / task / description

Added value: +"Concrete objective for Kimi to execute. Include the requested outcome and relevant constraints."

addedInput schema / properties / thinking / description

Added value: +"Optional Kimi thinking setting. Omit to use the bridge default; the managed pilot is configured for high thinking."

addedInput schema / properties / timeoutMs / description

Added value: +"Maximum time in milliseconds to wait for this call. A timeout returns control without aborting the Kimi session, so the same session can be waited on later."

First observedv0.3.0Sep 13, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already mark destructiveHint=true and idempotentHint=false. The description adds context: it waits for terminal states, may run commands and modify files, returns handoff/review data, and explicitly notes timeout behavior ('A timeout returns control without aborting the Kimi session'). It also discloses swarmEvidence behavior. No contradiction with annotations; adds valuable behavioral detail beyond the structured hints.

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 compact: three sentences cover purpose, usage differentiation, and key behavioral warnings. It is front-loaded with the core function and routes to the alternative, with no fluff. Every sentence contributes value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 10 parameters, a nested object, and no output schema, the description gives a solid overview but omits the exact return structure beyond 'handoff and review data' and 'structured swarmEvidence'. The timeout and dedupe behaviors are mentioned indirectly via schema. Slightly more detail on the return shape would help, but the core operation is adequately scoped for an agent to invoke it correctly.

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?

Schema coverage is 100%, with each parameter thoroughly described (e.g., dedupe object, model alias, timeoutMs). The description does not add parameter-level explanation beyond what the schema provides, but it does set expectations for the overall call (waiting, returning handoff data). Baseline 3 is appropriate since the schema carries the parameter documentation load.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb ('Start'), resource ('Kimi task'), and outcome ('wait for completion... return handoff and review data'). It explicitly distinguishes from kimi_delegate_task by naming the alternative and the condition ('when the caller needs immediate asynchronous control'), so an agent can select correctly without opening schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear guidance on when to prefer this tool over kimi_delegate_task, and warns that 'The task may run commands and modify files.' This covers primary usage context and a key exclusion (immediate async control), leaving little to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Delegate Kimi Task and Wait

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools