Skip to main content
Glama

dsh_delegate_task

Delegates a substantial independent module to a native teammate or task with goal, scope, constraints, and checks, then waits synchronously for completion.

Instructions

Optionally delegate a substantial independent module; reuse/spawn an official native teammate/task. Codex directly handles small integration fixes after first-round completion. Give a concise goal/scope/constraints/checks; no default reviewer. requestId is required; taskId+expectedRevision pin substantial rework. Omitted workspace resolves exact caller cwd. Finish necessary dispatches, then wait synchronously.

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": {
      "requestId": "<requestId>",
      "prompt": "<prompt>"
    },
    "name": "dsh_delegate_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
modelNo
promptYes
targetNo
taskIdNo
teamIdNo
subjectNo
providerNo
requestIdYes
workspaceNo
permissionNoNew Teams default to read-only; choose workspace-write for implementation at first open/delegate. Existing Team grants are immutable.
writeScopesNoWorkspace-relative paths or globs only, such as src/module.mjs; absolute paths are rejected by the official task board.
reasoningEffortNo
expectedRevisionNo

Output Schema

NameRequiredDescriptionDefault
okYes
dataNo
errorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.8.0-rc.8

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, so safety is partially covered. The description adds genuinely useful behavior beyond that: it blocks ('wait synchronously'), defaults workspace to caller cwd, pins rework via taskId+expectedRevision, and states there is no default reviewer. However, these are delivered as cryptic fragments and never explain what spawning vs reusing actually does to existing state.

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

Conciseness2/5

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

The description is short but structured as a run-on chain of semicolon fragments with no grouping or front-loading of the core action. Jargon like 'pin substantial rework' and 'Finish necessary dispatches' forces reinterpretation, so compactness costs clarity rather than buying it.

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?

An output schema exists, so return values need not be described, but for a 14-parameter mutation/delegation tool the description is far too thin: most parameters are unexplained, sibling differentiation is absent, and the reuse-vs-spawn decision is never made concrete. It leaves meaningful gaps an agent must close by guessing.

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

Parameters2/5

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

Schema description coverage is only 14%, so the description must compensate by explaining the 14 parameters. It names only a handful (requestId required, taskId+expectedRevision pinning, workspace defaulting), leaving name, model, target, teamId, subject, provider, prompt, permission and reasoningEffort effectively undocumented. Only two parameters (permission, writeScopes) get real explanation, and that comes from the schema, not the description.

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

Purpose3/5

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

The description gives a verb ('delegate') and a resource ('a substantial independent module' ... 'official native teammate/task'), but 'Optionally delegate' and 'reuse/spawn' leave the actual effect ambiguous. It does not distinguish itself from dsh_team or dsh_team_wait, so an agent cannot tell which tool to reach for without reading schemas.

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

Usage Guidelines3/5

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

'Codex directly handles small integration fixes after first-round completion' implies a when-not boundary (small fixes stay local), and 'substantial independent module' implies when-to-use. But there is no explicit alternative named, no prerequisite list, and the leading 'Optionally' weakens the guidance rather than clarifying it.

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