Skip to main content
Glama

create_task

Create a repo-scoped task to hand a plan to a local AI agent, with optional risk pre-assessment and independent verification.

Instructions

Create a repo-scoped task from exactly one source. For ChatGPT, prefer the guarded inspect_only, feature_small, or fix_tests template when it fits. A stale watcher preserves the task but returns execution_blocked and directs the client to health_check; otherwise call wait_for_task until terminal. Use execution_mode=assess_only to pre-assess risk and get an assessment_id without creating a task; then invoke the returned next_tool_call using only execution_mode=execute and the full assessment_id.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
goalNoRequired task goal when template is supplied.
agentNoConfigured local agent name. No agents are currently configured.
plan_idNoPlan ID from save_plan
templateNoBuilt-in guarded task template. ChatGPT should prefer inspect_only for diagnosis, feature_small for a scoped change, and fix_tests for known failing verification. Use with goal; rollback_scope_violation also requires source_task_id.
repo_pathNoRequired repository path inside workspaceRoot. No implicit workspace-root fallback is allowed.
plan_titleNoOptional title used when inline_plan is supplied.
request_idNoOptional create_task idempotency key. Reuse requires identical parameters, including requested_model.
inline_planNoInline Markdown plan. It is safety-checked and persisted as an auditable saved plan before task creation.
test_commandNoOptional exact-match verification command. Allowed: "cargo test", "npm run build", "npm run dist", "npm run doctor", "npm run format:check", "npm run lint", "npm run test", "npm test", "pnpm run build", "pnpm run dist", "pnpm run doctor", "pnpm run format:check", "pnpm run lint", "pnpm run test", "pnpm test", "pytest"
assessment_idNoAssessment ID from a prior assess_only call. When provided with execution_mode=execute, task parameters are loaded from the assessment record and locked to it. The full 128-bit ID (32 hex chars) must be provided; short IDs are display-only.
execution_modeNoassess_only: run deterministic risk checks and return an assessment_id without creating a task. execute (default): create and queue the task. When combined with assessment_id, the task parameters are loaded from the assessment record and freshness is revalidated.execute
source_task_idNoRequired source task for rollback_scope_violation review.
requested_modelNoOptional model override for the explicitly selected Agent. It is passed as one shell-free argv value and persisted as task evidence.
timeout_secondsNoTotal task timeout in seconds (default 900, max 3600)
verify_commandsNoRecommended exact-match commands PatchWarden runs independently after the agent exits. Repository-scoped commands are re-authorized after repo_path is resolved.
confirm_workspace_rootNoRequired only when repo_path resolves to a detected multi-project workspace root. This explicit acknowledgement is retained in task assessment evidence.
Behavior4/5

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

No annotations are provided, so the description bears full responsibility. It discloses behavior about stale watchers ('A stale watcher preserves the task but returns execution_blocked and directs the client to health_check') and instructs to call wait_for_task until terminal, which are beyond basic functionality.

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?

The description is 4 sentences, front-loads the purpose, and every sentence contributes unique information. It is efficient and well-structured without redundancy.

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?

Given 16 parameters and no annotations, the description covers critical workflows but omits context for many parameters (e.g., plan_id, inline_plan, test_command). It is sufficient for basic use but incomplete for full parameter integration.

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?

With 100% schema description coverage, the baseline is 3. The description adds value by explaining the interplay between execution_mode and assessment_id, and the requirement of source_task_id for rollback_scope_violation template, thus going beyond the schema descriptions.

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 clearly states 'Create a repo-scoped task from exactly one source.', which is specific and distinguishes it from sibling tools like create_subgoal_task. It also mentions templates and assess_only flow, further clarifying its purpose.

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 explicit guidance on when to use certain templates ('For ChatGPT, prefer the guarded inspect_only, feature_small, or fix_tests template when it fits') and outlines the two-step assess_only/execute workflow. It does not list alternatives or exclusions but gives clear context.

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