Skip to main content
Glama

Delegate a coding task (paid)

kimi_delegate

Offload coding tasks to Kimi in a throwaway git worktree and receive a reviewable diff. Inspect the changes, then apply them to your repository only after review.

Instructions

Delegate a coding task to Kimi (a different model) in an isolated git worktree, and get back a reviewable diff that is NOT applied to your tree.

PAID — this spends Kimi quota on every new call; use kimi_delegate_dry_run or kimi_status (both free) first if you only need to check scope or readiness.

Kimi edits files with workspace-write, but only inside a throwaway worktree seeded from your current tracked state. The returned diff is Kimi's changes; review it, then apply it yourself if you want it. Requires a git repo with at least one commit. Pass workspace_root (absolute).

NETWORK IS NOT BLOCKED: kimi has no sandbox, so a delegated task CAN reach the network — it may git push/fetch, run gh, curl, publish, or install dependencies, and it runs shell commands with your own user's privileges. Scope tasks accordingly and review the returned diff before applying it; the diff shows what changed in the worktree, not what else the run did. The Kimi model call also sends your task to your configured provider and lets Kimi read tracked files in the worktree and send their content. Kimi auto-loads the resolved workspace's AGENTS.md and discovers skills from its own config (including extra_skill_dirs, which may point outside the workspace). Skill names and descriptions are exposed to the model up front, so that content can be sent even if your prompt never mentions it. The isolation setting does not suppress any of it: kimi's built-in skills always load, and AGENTS.md is read regardless.

Your inputs are sent raw and unredacted. Secret redaction is best-effort and covers the gathered diff and Kimi's returned output — not what you type, and not the files Kimi reads for itself.

Progress & recovery: blocks up to the resolved deadline (timeout_seconds, clamped 10-600s; when omitted, the server-configured value, built-in default 300s). If that deadline expires the run is terminated and its partial output is not recoverable or resumable, so for a substantial or multi-file task that may exceed it, prefer kimi_delegate_async (a background job, built-in default 1800s deadline; poll kimi_job_status). Coarse notifications/progress streams while it blocks when your client requests it; some MCP clients background a long call before the deadline, so timeout_seconds bounds the run, not necessarily the inline wait — either way the detached run (meta.job_id) is recoverable via kimi_job_listkimi_job_statuskimi_job_result.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
taskYesThe coding task for Kimi to implement inside a throwaway git worktree; the resulting diff is returned for review, not applied to your tree. Must be non-blank: empty or whitespace-only is rejected before any model call.
modelNoOverride the Kimi model slug for this call; defaults to the server/Kimi default when unset.
detailNoResponse verbosity: 'summary' (default) omits the raw model text; 'full' includes it.summary
isolationNoWhich skills Kimi loads: 'inherit' (own user/project discovery) or 'ignore-skills' (empty dir). Built-ins load either way; this reduces loading, not isolation. Default: server-configured, per kimi_status. More: kimi://params.
workspace_rootNoAbsolute path to the target repo root — pass it to target the intended repo (MCP roots are unavailable); otherwise the call falls back to the server's own cwd and sets meta.workspace_warning.
idempotency_keyNoOptional dedup key scoped to THIS tool + workspace. Same key + same args replays the prior result with no new spend; different args are refused (idempotency_conflict). Sync and _async are separate tools and never share a key. Omit for none; retention is bounded. Lifecycle: kimi://params.
timeout_secondsNoPer-call wall-clock timeout in seconds, clamped to 10..600 (out-of-range values are coerced, not rejected). Defaults to the server's configured timeout.
reasoning_effortNoOverride the Kimi reasoning effort for this call (a model_reasoning_effort override); omit or pass null for the server default (MOONBRIDGE_REASONING_EFFORT) or Kimi's own resolution. An open, per-model string the backend validates at run time — commonly minimal|low|medium|high|xhigh; kimi_models lists each model's advertised set (advisory). Rejection and bounds detail: kimi://params.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYes
Install Server

TDQS

A4.8/5.0
Behavior5/5

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

The description goes far beyond annotations. It discloses the paid/quota cost, the non-blocked network and lack of sandbox, execution with the user's own privileges, that AGENTS.md and skills are loaded even with isolation settings, raw input exposure, best-effort redaction limits, timeout/deadline behavior, and non-recoverable partial output. Annotations already mark readOnlyHint=false and openWorldHint=true, and the description expands on that meaningfully.

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 dense and information-rich, with critical facts front-loaded: the headline diff-not-applied behavior, the paid cost, and the free alternatives. It is longer than average, but every section covers high-stakes facts an agent needs before invoking a paid, un-sandboxed, potentially network-accessible tool. Slight structural improvement could consolidate the warnings, but overall it is well organized with clear topic shifts.

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

Completeness5/5

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

Given the tool's genuine complexity, a high-stakes paid model delegation with 8 parameters, no sandbox, and many sibling alternatives, the description covers prerequisites, cost, security boundaries, failure modes, timeouts, recovery paths, and routing to async variants. An output schema exists, so the description need not enumerate return values. This is as complete as an agent could reasonably need.

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 description coverage is 100%, so the schema already documents each parameter. However, the description adds context beyond the schema, especially for workspace_root (MCP roots unavailable, fallback to server cwd, workspace_warning), isolation (built-ins load either way), idempotency_key (scoped to tool+workspace, replay semantics, conflict refusal), and timeout_seconds (clamping behavior). It also explains how parameters relate to runtime behavior (e.g., timeout_seconds bounds the run, not necessarily the inline wait).

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 (delegate), resource (a coding task to Kimi), and the key behavioral outcome (a reviewable diff that is not applied to the tree). It is clearly distinguished from siblings by naming alternatives like kimi_delegate_dry_run, kimi_status, and kimi_delegate_async.

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 explicitly says when to use the tool (when you want Kimi to implement a coding task and inspect the diff before applying), when to avoid it (for mere scope/readiness checks, use kimi_delegate_dry_run/kimi_status), and when to use an alternative (kimi_delegate_async for substantial tasks likely to exceed the deadline). It also notes the workspace_root requirement and the prerequisite of a git repo with at least one commit.

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

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/briandconnelly/moonbridge'

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