PatchWarden

create_goal

Create a goal session for managing multi-task objectives with subgoal dependencies, generating structured goal documentation and status tracking for auditable execution.

Instructions

v0.8.0: Create a Goal Session for managing a multi-task objective with subgoal dependencies. Generates a structured directory under .patchwarden/goals/{goal_id}/ with GOAL.md, GOALS.md, and goal_status.json. Use list_goals to enumerate existing goals and read_goal to inspect details.

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": {
      "title": "<title>",
      "goal_description": "<goal_description>",
      "repo_path": "<repo_path>"
    },
    "name": "create_goal"
  }
}

Input Schema

Name	Required	Description
`title`	Yes	Goal title (human-readable).
`repo_path`	Yes	Repository path inside workspaceRoot. Must be inside the configured workspace.
`goal_description`	Yes	Markdown description of the goal, success criteria, and context.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.5.0Jul 8, 2026

TDQS

A4.2/5.0

Behavior4/5

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

No annotations provided, but description discloses side effects: creates a structured directory with specific files. It adds behavioral context beyond the schema. Minor lack of detail on permissions or reversibility.

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 sentences with front-loaded purpose and context about output structure and sibling tools. Every sentence is valuable 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?

Fairly complete given complexity: mentions files created (.patchwarden/goals/{goal_id}/ with GOAL.md, GOALS.md, goal_status.json). No output schema, so return values not described, but overall adequate.

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 coverage is 100%, so baseline 3. Description does not add significant meaning to 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?

Description clearly states 'Create a Goal Session' with specific verb and resource, and mentions generating a structured directory, distinguishing it from siblings like list_goals and read_goal.

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?

Explicitly recommends using list_goals and read_goal for enumeration and inspection, providing clear context for when not to use this tool. Does not explicitly state exclusions but is sufficient.

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

Deploy Server