Skip to main content
Glama

create_subgoal_task

Create a subgoal in a goal session and launch its associated task atomically, with dependencies on accepted subgoals.

Instructions

v0.8.0: Create a subgoal within a Goal Session and immediately launch an associated task. Atomically: addSubgoal → create_task → linkTask → mark subgoal running. The subgoal depends_on other subgoals (by id) which must be accepted before suggest_next_subgoal returns it.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
goalNoTask goal when template is supplied.
agentNoAgent name.
scopeNoAllowed file/directory scope.
goal_idYesGoal ID to add the subgoal to.
plan_idNoPlan ID from save_plan. One of plan_id/inline_plan/template+goal is required.
templateNoBuilt-in task template. Use with goal.
forbiddenNoForbidden file/directory paths.
repo_pathYesRepository path inside workspaceRoot.
depends_onNoSubgoal IDs this subgoal depends on. Dependencies must be accepted before this subgoal is suggested.
plan_titleNoOptional title for inline_plan.
inline_planNoInline Markdown plan.
test_commandNoVerification command.
verificationNoAcceptance verification commands.
done_evidenceNoRequired done evidence files.
subgoal_titleYesTitle of the new subgoal.
requested_modelNoOptional model override for the explicitly selected Agent.
timeout_secondsNoTask timeout in seconds.
verify_commandsNoAdditional verification commands.
isolate_worktreeNov1.0.0: If true (default), create the task in an isolated git worktree under _workspacetrees/. Set false to run in the main workspace (v0.8.0 behavior)
Behavior3/5

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

With no annotations, the description carries the full burden. It discloses atomic steps and dependency requirement, but lacks details on failure rollback, idempotency, or auth needs. Adequate but not rich.

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?

Two concise sentences with no wasted words. Purpose and key behavioral trait are front-loaded. Efficient and clear.

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

Completeness3/5

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

Despite 19 parameters and no output schema, the description only covers atomicity and dependencies. It does not explain return values, error conditions, or parameter relationships, leaving gaps for a complex tool.

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. Description adds no new parameter-level insight beyond what the schema already provides; it merely restates dependency behavior.

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?

Description clearly states the tool creates a subgoal and immediately launches an associated task, with an atomic sequence. It distinguishes from sibling tools like create_goal and create_task by combining both actions.

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?

Provides context about dependencies and the atomic nature, implying when to use it. However, no explicit exclusions or alternatives are mentioned, so it's not a perfect 5.

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/jiezeng2004-design/PatchWarden'

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