Skip to main content
Glama
rnd-pro
by rnd-pro

delegate_to_group

Delegate tasks to a named agent group, spawning agents with shared config and returning task IDs for immediate, non-blocking execution. Supports parallel spawning via count parameter.

Instructions

Delegate a task to a named agent group. Spawns agents with the group's shared config (runner, skill, policy). Use count to launch multiple agents in parallel (fractal orchestration).

Returns array of task_ids immediately (non-blocking). Use get_task_result to check each.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cwdNoWorking directory. Defaults to current working directory.
countNoNumber of agents to spawn. Default: 1.
filesNoKnown relevant file paths used as structured focus hints for context resolution. May include paths attached in the UI.
groupYesGroup name to delegate to.
modelNoModel override for this group delegation. Default: group profile/model.
promptYesTask description for the agents.
chat_idNoExisting chat ID to bind child tasks to.
timeoutNoTimeout in seconds. Overrides group default.
providerNoCLI provider override for this group delegation. Default: group provider or codex.
agent_slugNoAgent role slug passed to child tasks.
session_idNoProvider session/thread ID passed through for resumed tasks.
focus_graphNoPortal-provided compact project-graph focus context for files[], including symbols, imports, dependencies, and web component summaries when present. Usually injected automatically; direct callers should prefer files[].
serviceTierNoService tier for Codex. Codex maps to service_tier.
context_modeNoContext package mode for delegated agents. auto injects the metadata-first resolved context package. off disables injection. Default: auto.
include_dirsNoScope directories override for child tasks. Default: group include_dirs.
on_wait_hintNoOptional wait hint shown while the task runs.
allowed_toolsNoProvider tool allowlist override for compatible runners.
approval_modeNoAccess mode override passed to child tasks.
parent_chat_idNoParent chat ID used to create/bind child task chats.
reasoningEffortNoProvider reasoning effort. Codex accepts the selected model value and maps it to model_reasoning_effort. Claude Code accepts low, medium, high, xhigh, or max and maps it to --effort.
Behavior3/5

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

No annotations are provided, so the description carries full burden. It discloses key behavior: returns array of task_ids immediately (non-blocking), and spawns agents with group config. However, it does not mention error conditions, prerequisites, or side effects like permission needs.

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?

Three sentences: first states core purpose, second gives a usage hint, third explains return behavior. No unnecessary words, well-structured, and efficient.

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?

For a tool with 20 parameters and no output schema, the description covers the overarching behavior (delegation, parallelism, non-blocking). It misses details on parameter interactions but schema provides per-parameter descriptions, making the overall definition reasonably complete.

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 description coverage is 100%, so baseline is 3. The description adds value by explaining 'count' for parallel execution and the return behavior, but does not elaborate on many other parameters beyond what schema already provides.

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 uses specific verb 'delegate' and resource 'named agent group', and mentions 'spawns agents with shared config'. This clearly distinguishes from siblings like delegate_task (which likely delegates to a single agent) and delegate_task_readonly.

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

Usage Guidelines4/5

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

The description provides context for when to use 'count' for parallel spawning and notes the non-blocking nature with a pointer to get_task_result. However, it does not explicitly state when not to use this tool or compare with siblings.

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/rnd-pro/agent-pool-mcp'

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