Codex Free Worker

Overview Schema Source Related Servers Discussions Admin

delegate_task

Delegate bounded repository tasks—failing tests, CI logs, build/fix/rerun loops—to OpenCode for inspection and iteration, returning a compact result with inspect/fix modes and escalation flag.

Instructions

Delegate a bounded repository task to OpenCode.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "task": "<task>",
      "cwd": "<cwd>"
    },
    "name": "delegate_task"
  }
}

Input Schema

Name	Required	Default
`cwd`	Yes
`mode`	No	inspect
`task`	Yes

Output Schema

Name	Required	Description	Default
`checks`	No
`status`	Yes
`summary`	Yes
`changed_files`	No
`decision_required`	No
`relevant_locations`	No
`needs_main_model_decision`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 27, 2026

TDQS

C2.4/5.0

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 behavioral burden. It hints at scope limitation with 'bounded', but does not disclose permissions, side effects, whether fix mutates the repository, rate limits, or other operational traits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The single sentence is front-loaded and free of filler, but it is too terse for a three-parameter tool with behavioral implications. Its brevity reflects under-specification rather than efficient completeness.

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

Completeness1/5

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

Although an output schema exists and return values need not be explained, the description omits usage guidance, parameter semantics, and behavioral context. With no annotations and 0% schema description coverage, it is nearly inadequate for this tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate. It mentions no parameters at all and does not explain task, cwd, or the inspect/fix enum, leaving all parameter meaning to undocumented schema fields.

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 states a specific verb and resource (delegate a repository task) and names the target (OpenCode) with a scope qualifier (bounded). This is clear, though it does not explain what OpenCode is or what delegation entails.

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?

There is no guidance on when to use this tool versus alternatives, nor when to choose inspect versus fix. The intended context is only implied by 'bounded repository task'.

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

Deploy Server

Other Tools

delegate_taskC