@vibescope/mcp-server 0.4.5 → 0.4.7

package/dist/tools/bodies-of-work.js

@@ -18,7 +18,7 @@
 export const bodiesOfWorkTools = [
     {
         name: 'create_body_of_work',
-        description: `Create a new body of work to group tasks into phases (pre/core/post).
+        description: `Create a new body of work to group tasks into phases (pre/core/post).
 Bodies of work allow organizing related tasks with optional auto-deployment on completion.`,
         inputSchema: {
             type: 'object',
@@ -148,7 +148,7 @@ Bodies of work allow organizing related tasks with optional auto-deployment on c
     },
     {
         name: 'add_task_to_body_of_work',
-        description: `Add a task to a body of work in a specific phase.
+        description: `Add a task to a body of work in a specific phase.
 Phases control execution order: pre tasks run first, then core, then post.`,
         inputSchema: {
             type: 'object',
@@ -190,7 +190,7 @@ Phases control execution order: pre tasks run first, then core, then post.`,
     },
     {
         name: 'activate_body_of_work',
-        description: `Activate a draft body of work to start execution.
+        description: `Activate a draft body of work to start execution.
 Requires at least one task. Once active, tasks can be worked on following phase order.`,
         inputSchema: {
             type: 'object',
@@ -205,7 +205,7 @@ Requires at least one task. Once active, tasks can be worked on following phase
     },
     {
         name: 'add_task_dependency',
-        description: `Add a dependency between tasks in a body of work.
+        description: `Add a dependency between tasks in a body of work.
 The dependent task cannot start until the dependency is completed. Prevents circular dependencies.`,
         inputSchema: {
             type: 'object',
@@ -263,8 +263,8 @@ The dependent task cannot start until the dependency is completed. Prevents circ
     },
     {
         name: 'get_next_body_of_work_task',
-        description: `Get the next available task from a body of work.
-Considers phase order (pre → core → post) and task dependencies.
+        description: `Get the next available task from a body of work.
+Considers phase order (pre → core → post) and task dependencies.
 Only returns tasks where all dependencies are completed.`,
         inputSchema: {
             type: 'object',

package/dist/tools/chat.d.ts

@@ -2,6 +2,7 @@
  * Project chat tools:
  * - send_project_message
  * - get_project_messages
+ * - post_progress
  */
 import type { Tool } from './types.js';
 export declare const chatTools: Tool[];

package/dist/tools/chat.js

@@ -2,6 +2,7 @@
  * Project chat tools:
  * - send_project_message
  * - get_project_messages
+ * - post_progress
  */
 export const chatTools = [
     {
@@ -40,4 +41,27 @@ export const chatTools = [
             required: ['project_id'],
         },
     },
+    {
+        name: 'post_progress',
+        description: 'Post a structured progress update to the project chat. Use this at key milestones during your work: when starting a task, creating a PR, hitting a blocker, or completing a task. Messages are attributed to your agent and shown with a type icon.',
+        inputSchema: {
+            type: 'object',
+            properties: {
+                project_id: {
+                    type: 'string',
+                    description: 'Project UUID',
+                },
+                message: {
+                    type: 'string',
+                    description: 'Progress update message (supports markdown)',
+                },
+                type: {
+                    type: 'string',
+                    enum: ['info', 'milestone', 'blocker', 'question'],
+                    description: 'Type of update: info (general update), milestone (key achievement), blocker (something blocking progress), question (asking for input). Defaults to info.',
+                },
+            },
+            required: ['project_id', 'message'],
+        },
+    },
 ];

package/dist/tools/cloud-agents.js

@@ -8,16 +8,16 @@
 export const cloudAgentTools = [
     {
         name: 'cleanup_stale_cloud_agents',
-        description: `Clean up stale cloud agents that failed to start or lost connection.
-
-Finds agents stuck in 'starting' status (or optionally 'running' with no heartbeat) 
-and marks them as failed. Only operates on the current session's project.
-
-Use this when:
-- You see agents stuck in "starting" status on the dashboard
-- Cloud agents failed to spawn but weren't cleaned up
-- You want to clear ghost agents from a previous session
-
+        description: `Clean up stale cloud agents that failed to start or lost connection.
+
+Finds agents stuck in 'starting' status (or optionally 'running' with no heartbeat) 
+and marks them as failed. Only operates on the current session's project.
+
+Use this when:
+- You see agents stuck in "starting" status on the dashboard
+- Cloud agents failed to spawn but weren't cleaned up
+- You want to clear ghost agents from a previous session
+
 SECURITY: This only affects agents in YOUR current project. Cannot access other users' projects.`,
         inputSchema: {
             type: 'object',
@@ -44,9 +44,9 @@ SECURITY: This only affects agents in YOUR current project. Cannot access other
     },
     {
         name: 'list_cloud_agents',
-        description: `List cloud agents for a project.
-
-Returns all spawned cloud agents for the project with their current status.
+        description: `List cloud agents for a project.
+
+Returns all spawned cloud agents for the project with their current status.
 Use this to check the state of cloud agents before/after cleanup.`,
         inputSchema: {
             type: 'object',
@@ -66,15 +66,15 @@ Use this to check the state of cloud agents before/after cleanup.`,
     },
     {
         name: 'update_agent_status',
-        description: `Report what you're currently doing. This updates the status message shown on the dashboard.
-
-Call this at key milestones during boot and work:
-- "Installing dependencies..."
-- "Running start_work_session..."
-- "Working on: <task title>"
-- "Running tests..."
-- "Committing changes..."
-
+        description: `Report what you're currently doing. This updates the status message shown on the dashboard.
+
+Call this at key milestones during boot and work:
+- "Installing dependencies..."
+- "Running start_work_session..."
+- "Working on: <task title>"
+- "Running tests..."
+- "Committing changes..."
+
 Keep messages short (under 80 chars). The dashboard shows this in real-time.`,
         inputSchema: {
             type: 'object',

package/dist/tools/features.d.ts

@@ -0,0 +1,13 @@
+/**
+ * Feature Tool Definitions
+ *
+ * Tools for managing feature specs (between ideas and tasks):
+ * - add_feature
+ * - update_feature
+ * - get_feature
+ * - get_features
+ * - delete_feature
+ * - link_idea_to_feature
+ */
+import type { Tool } from './types.js';
+export declare const featureTools: Tool[];

package/dist/tools/features.js

@@ -0,0 +1,151 @@
+/**
+ * Feature Tool Definitions
+ *
+ * Tools for managing feature specs (between ideas and tasks):
+ * - add_feature
+ * - update_feature
+ * - get_feature
+ * - get_features
+ * - delete_feature
+ * - link_idea_to_feature
+ */
+export const featureTools = [
+    {
+        name: 'add_feature',
+        description: `Create a new feature spec. Features sit between ideas (quick thoughts) and tasks (actionable work). Use features to flesh out a concept into a full spec before breaking it into tasks. Starts as 'draft'.`,
+        inputSchema: {
+            type: 'object',
+            properties: {
+                project_id: {
+                    type: 'string',
+                    description: 'Project UUID',
+                },
+                title: {
+                    type: 'string',
+                    description: 'Feature title',
+                },
+                body: {
+                    type: 'string',
+                    description: 'Markdown spec content — requirements, user stories, acceptance criteria, technical approach',
+                },
+                priority: {
+                    type: 'number',
+                    minimum: 1,
+                    maximum: 5,
+                    description: 'Priority 1-5 (1 = highest, default: 2)',
+                },
+            },
+            required: ['project_id', 'title'],
+        },
+    },
+    {
+        name: 'update_feature',
+        description: `Update a feature's title, body, status, or priority.`,
+        inputSchema: {
+            type: 'object',
+            properties: {
+                feature_id: {
+                    type: 'string',
+                    description: 'Feature UUID',
+                },
+                title: {
+                    type: 'string',
+                    description: 'Updated title',
+                },
+                body: {
+                    type: 'string',
+                    description: 'Updated markdown spec content',
+                },
+                status: {
+                    type: 'string',
+                    enum: ['draft', 'refining', 'specced', 'ready', 'building', 'shipped'],
+                    description: 'New status',
+                },
+                priority: {
+                    type: 'number',
+                    minimum: 1,
+                    maximum: 5,
+                    description: 'Updated priority (1 = highest)',
+                },
+            },
+            required: ['feature_id'],
+        },
+    },
+    {
+        name: 'get_feature',
+        description: `Get a single feature by ID. More token-efficient than get_features when you need details for a specific feature.`,
+        inputSchema: {
+            type: 'object',
+            properties: {
+                feature_id: {
+                    type: 'string',
+                    description: 'Feature UUID',
+                },
+            },
+            required: ['feature_id'],
+        },
+    },
+    {
+        name: 'get_features',
+        description: `Get features for a project, optionally filtered by status. Features represent fleshed-out specs between ideas and tasks.`,
+        inputSchema: {
+            type: 'object',
+            properties: {
+                project_id: {
+                    type: 'string',
+                    description: 'Project UUID',
+                },
+                status: {
+                    type: 'string',
+                    enum: ['draft', 'refining', 'specced', 'ready', 'building', 'shipped'],
+                    description: 'Filter by status (optional)',
+                },
+                limit: {
+                    type: 'number',
+                    description: 'Max number of features to return (default 20, max 100)',
+                },
+                offset: {
+                    type: 'number',
+                    description: 'Number of features to skip for pagination (default 0)',
+                },
+                search_query: {
+                    type: 'string',
+                    description: 'Search features by title or body content',
+                },
+            },
+            required: ['project_id'],
+        },
+    },
+    {
+        name: 'delete_feature',
+        description: `Delete a feature spec. This also removes all linked idea and task associations.`,
+        inputSchema: {
+            type: 'object',
+            properties: {
+                feature_id: {
+                    type: 'string',
+                    description: 'Feature UUID',
+                },
+            },
+            required: ['feature_id'],
+        },
+    },
+    {
+        name: 'link_idea_to_feature',
+        description: `Link an existing idea to a feature spec. This associates the idea as inspiration for the feature.`,
+        inputSchema: {
+            type: 'object',
+            properties: {
+                feature_id: {
+                    type: 'string',
+                    description: 'Feature UUID',
+                },
+                idea_id: {
+                    type: 'string',
+                    description: 'Idea UUID to link',
+                },
+            },
+            required: ['feature_id', 'idea_id'],
+        },
+    },
+];

package/dist/tools/index.d.ts

@@ -31,6 +31,7 @@ import { gitIssueTools } from './git-issues.js';
 import { connectorTools } from './connectors.js';
 import { cloudAgentTools } from './cloud-agents.js';
 import { versionTools } from './version.js';
+import { featureTools } from './features.js';
 /**
  * All MCP tool definitions combined
  */
@@ -69,5 +70,6 @@ export declare const toolCategories: {
     readonly connectors: string[];
     readonly cloudAgents: string[];
     readonly version: string[];
+    readonly features: string[];
 };
-export { sessionTools, costTools, discoveryTools, worktreeTools, projectTools, taskTools, progressTools, blockerTools, decisionTools, ideaTools, findingTools, validationTools, deploymentTools, fallbackTools, requestTools, milestoneTools, bodiesOfWorkTools, organizationTools, fileCheckoutTools, roleTools, sprintTools, gitIssueTools, connectorTools, cloudAgentTools, versionTools, };
+export { sessionTools, costTools, discoveryTools, worktreeTools, projectTools, taskTools, progressTools, blockerTools, decisionTools, ideaTools, findingTools, validationTools, deploymentTools, fallbackTools, requestTools, milestoneTools, bodiesOfWorkTools, organizationTools, fileCheckoutTools, roleTools, sprintTools, gitIssueTools, connectorTools, cloudAgentTools, versionTools, featureTools, };

package/dist/tools/index.js

@@ -31,6 +31,7 @@ import { connectorTools } from './connectors.js';
 import { cloudAgentTools } from './cloud-agents.js';
 import { versionTools } from './version.js';
 import { chatTools } from './chat.js';
+import { featureTools } from './features.js';
 /**
  * All MCP tool definitions combined
  */
@@ -61,6 +62,7 @@ export const tools = [
     ...cloudAgentTools,
     ...versionTools,
     ...chatTools,
+    ...featureTools,
 ];
 /**
  * Build the complete tool list from all domain modules
@@ -98,6 +100,7 @@ export const toolCategories = {
     connectors: connectorTools.map((t) => t.name),
     cloudAgents: cloudAgentTools.map((t) => t.name),
     version: versionTools.map((t) => t.name),
+    features: featureTools.map((t) => t.name),
 };
 // Re-export domain tools for selective imports
-export { sessionTools, costTools, discoveryTools, worktreeTools, projectTools, taskTools, progressTools, blockerTools, decisionTools, ideaTools, findingTools, validationTools, deploymentTools, fallbackTools, requestTools, milestoneTools, bodiesOfWorkTools, organizationTools, fileCheckoutTools, roleTools, sprintTools, gitIssueTools, connectorTools, cloudAgentTools, versionTools, };
+export { sessionTools, costTools, discoveryTools, worktreeTools, projectTools, taskTools, progressTools, blockerTools, decisionTools, ideaTools, findingTools, validationTools, deploymentTools, fallbackTools, requestTools, milestoneTools, bodiesOfWorkTools, organizationTools, fileCheckoutTools, roleTools, sprintTools, gitIssueTools, connectorTools, cloudAgentTools, versionTools, featureTools, };

package/dist/tools/milestones.js

@@ -11,8 +11,8 @@
 export const milestoneTools = [
     {
         name: 'add_milestone',
-        description: `Add a milestone to a task.
-Milestones help break down large tasks into smaller trackable steps.
+        description: `Add a milestone to a task.
+Milestones help break down large tasks into smaller trackable steps.
 Use this to show progress on complex tasks and help gauge completion.`,
         inputSchema: {
             type: 'object',

package/dist/tools/project.js

@@ -160,6 +160,10 @@ export const projectTools = [
                     items: { type: 'string' },
                     description: 'Array of preferred fallback activities (e.g., ["code_review", "security_review"]). Null means all allowed.',
                 },
+                allow_agent_task_creation: {
+                    type: 'boolean',
+                    description: 'Allow agents to create tasks via add_task (default: false). When disabled, agents receive a helpful error directing them to log suggestions in their completion summary instead.',
+                },
             },
             required: ['project_id'],
         },

package/dist/tools/requests.js

@@ -45,7 +45,7 @@ export const requestTools = [
     },
     {
         name: 'answer_question',
-        description: `Answer a question from the user. Use this when the user has asked a question via the dashboard.
+        description: `Answer a question from the user. Use this when the user has asked a question via the dashboard.
 The answer will be displayed to the user and the question marked as answered.`,
         inputSchema: {
             type: 'object',

package/dist/tools/session.js

@@ -14,11 +14,11 @@
 export const sessionTools = [
     {
         name: 'start_work_session',
-        description: `CALL THIS FIRST when beginning work on a project.
-Returns session info, persona, role, and next_task. Start the next_task IMMEDIATELY without asking the user.
-
-IMPORTANT: If the user gives you direct work that isn't tracked as a task (e.g., "add feature X", "fix bug Y"), you MUST call add_task() first to create a task before starting work. This ensures all work is tracked and visible on the dashboard.
-
+        description: `CALL THIS FIRST when beginning work on a project.
+Returns session info, persona, role, and next_task. Start the next_task IMMEDIATELY without asking the user.
+
+IMPORTANT: If the user gives you direct work that isn't tracked as a task (e.g., "add feature X", "fix bug Y"), you MUST call add_task() first to create a task before starting work. This ensures all work is tracked and visible on the dashboard.
+
 Use mode:'full' for complete context, mode:'lite' (default) for minimal tokens.`,
         inputSchema: {
             type: 'object',
@@ -61,8 +61,8 @@ Use mode:'full' for complete context, mode:'lite' (default) for minimal tokens.`
     },
     {
         name: 'confirm_agent_setup',
-        description: `Confirm that agent setup is complete for this project. Call this after creating your agent's configuration file (e.g., .claude/CLAUDE.md, .gemini/GEMINI.md).
-
+        description: `Confirm that agent setup is complete for this project. Call this after creating your agent's configuration file (e.g., .claude/CLAUDE.md, .gemini/GEMINI.md).
+
 This marks your agent type as fully onboarded to the project, so you won't receive setup instructions again.`,
         inputSchema: {
             type: 'object',
@@ -104,10 +104,10 @@ This marks your agent type as fully onboarded to the project, so you won't recei
     },
     {
         name: 'report_token_usage',
-        description: `Report actual Claude API token usage for accurate cost tracking.
-
-IMPORTANT: MCP can only estimate tokens from tool I/O (~1-5% of actual usage). Call this tool after each API response to report actual usage from the Claude API response headers.
-
+        description: `Report actual Claude API token usage for accurate cost tracking.
+
+IMPORTANT: MCP can only estimate tokens from tool I/O (~1-5% of actual usage). Call this tool after each API response to report actual usage from the Claude API response headers.
+
 The Claude API response includes 'usage.input_tokens' and 'usage.output_tokens' - pass those values here for accurate cost attribution.`,
         inputSchema: {
             type: 'object',

package/dist/tools/sprints.js

@@ -17,7 +17,7 @@
 export const sprintTools = [
     {
         name: 'create_sprint',
-        description: `Create a new sprint. Sprints are time-bounded bodies of work with velocity tracking.
+        description: `Create a new sprint. Sprints are time-bounded bodies of work with velocity tracking.
 Sprints start in 'planning' status where tasks can be added with story points.`,
         inputSchema: {
             type: 'object',
@@ -106,8 +106,8 @@ Sprints start in 'planning' status where tasks can be added with story points.`,
     },
     {
         name: 'get_sprint',
-        description: `Get a sprint with all its tasks organized by phase (pre/core/post).
-Includes progress percentage, velocity points, and committed points.
+        description: `Get a sprint with all its tasks organized by phase (pre/core/post).
+Includes progress percentage, velocity points, and committed points.
 Use summary_only: true to get task counts and next task instead of full task arrays (saves tokens).`,
         inputSchema: {
             type: 'object',
@@ -126,7 +126,7 @@ Use summary_only: true to get task counts and next task instead of full task arr
     },
     {
         name: 'get_sprints',
-        description: `List sprints for a project with velocity metrics.
+        description: `List sprints for a project with velocity metrics.
 Returns sprints sorted by sprint_number descending (most recent first).`,
         inputSchema: {
             type: 'object',
@@ -164,7 +164,7 @@ Returns sprints sorted by sprint_number descending (most recent first).`,
     },
     {
         name: 'start_sprint',
-        description: `Start a sprint. Transitions from 'planning' to 'active' status.
+        description: `Start a sprint. Transitions from 'planning' to 'active' status.
 Locks the committed_points at the current total story points.`,
         inputSchema: {
             type: 'object',
@@ -179,7 +179,7 @@ Locks the committed_points at the current total story points.`,
     },
     {
         name: 'complete_sprint',
-        description: `Complete a sprint. Handles retrospective phase and auto-deployment if configured.
+        description: `Complete a sprint. Handles retrospective phase and auto-deployment if configured.
 Status flow: active → in_review → retrospective → completed`,
         inputSchema: {
             type: 'object',
@@ -202,7 +202,7 @@ Status flow: active → in_review → retrospective → completed`,
     },
     {
         name: 'add_task_to_sprint',
-        description: `Add a task to a sprint with optional story points.
+        description: `Add a task to a sprint with optional story points.
 Tasks can be added during 'planning' status. Story points contribute to committed_points.`,
         inputSchema: {
             type: 'object',
@@ -248,7 +248,7 @@ Tasks can be added during 'planning' status. Story points contribute to committe
     },
     {
         name: 'get_sprint_backlog',
-        description: `Get tasks from backlog/pending that can be added to a sprint with pagination.
+        description: `Get tasks from backlog/pending that can be added to a sprint with pagination.
 Returns tasks not already assigned to any body of work or sprint.`,
         inputSchema: {
             type: 'object',
@@ -275,7 +275,7 @@ Returns tasks not already assigned to any body of work or sprint.`,
     },
     {
         name: 'get_sprint_velocity',
-        description: `Get velocity metrics for completed sprints.
+        description: `Get velocity metrics for completed sprints.
 Returns committed vs completed points and average velocity.`,
         inputSchema: {
             type: 'object',

package/dist/tools/tasks.js

@@ -164,8 +164,8 @@ export const taskTools = [
     },
     {
         name: 'get_next_task',
-        description: `Get highest priority pending task. Start it IMMEDIATELY by calling update_task(task_id, status: "in_progress").
-
+        description: `Get highest priority pending task. Start it IMMEDIATELY by calling update_task(task_id, status: "in_progress").
+
 Do NOT ask the user for permission. Follow the directive in the response.`,
         inputSchema: {
             type: 'object',
@@ -180,12 +180,12 @@ Do NOT ask the user for permission. Follow the directive in the response.`,
     },
     {
         name: 'add_task',
-        description: `Add a new task. Priority 1=highest, 5=lowest. Include estimated_minutes. Use blocking=true for deployment finalization tasks that must complete before other work.
-
-WHEN TO USE: If the user gives you work directly (e.g., "implement feature X", "fix this bug") that isn't already tracked as a task in Vibescope, you MUST create a task first using this tool. This ensures:
-- The work is visible on the dashboard
-- Progress can be tracked
-- Other agents won't duplicate the work
+        description: `Add a new task. Priority 1=highest, 5=lowest. Include estimated_minutes. Use blocking=true for deployment finalization tasks that must complete before other work.
+
+WHEN TO USE: If the user gives you work directly (e.g., "implement feature X", "fix this bug") that isn't already tracked as a task in Vibescope, you MUST create a task first using this tool. This ensures:
+- The work is visible on the dashboard
+- Progress can be tracked
+- Other agents won't duplicate the work
 - The human can see what you're working on`,
         inputSchema: {
             type: 'object',
@@ -228,17 +228,17 @@ WHEN TO USE: If the user gives you work directly (e.g., "implement feature X", "
     },
     {
         name: 'update_task',
-        description: `Update task status, progress, or details. Include progress_note with progress_percentage.
-
-CRITICAL - WORKTREE REQUIRED: For projects using github-flow or git-flow, you MUST use a git worktree to isolate your work. This prevents conflicts with other agents working on the same repository.
-
-When setting status to "in_progress":
-1. Create worktree FIRST: git worktree add ../PROJECT-PERSONA-task-desc -b feature/TASKID-description BASE_BRANCH
-2. cd into the worktree directory
-3. THEN call update_task with git_branch AND worktree_path
-
-Example: update_task(task_id, status: "in_progress", git_branch: "feature/abc123-add-login", worktree_path: "../MyProject-Edge-add-login")
-
+        description: `Update task status, progress, or details. Include progress_note with progress_percentage.
+
+CRITICAL - WORKTREE REQUIRED: For projects using github-flow or git-flow, you MUST use a git worktree to isolate your work. This prevents conflicts with other agents working on the same repository.
+
+When setting status to "in_progress":
+1. Create worktree FIRST: git worktree add ../PROJECT-PERSONA-task-desc -b feature/TASKID-description BASE_BRANCH
+2. cd into the worktree directory
+3. THEN call update_task with git_branch AND worktree_path
+
+Example: update_task(task_id, status: "in_progress", git_branch: "feature/abc123-add-login", worktree_path: "../MyProject-Edge-add-login")
+
 For projects without git branching (trunk-based or none), use skip_worktree_requirement: true.`,
         inputSchema: {
             type: 'object',
@@ -306,18 +306,18 @@ For projects without git branching (trunk-based or none), use skip_worktree_requ
     },
     {
         name: 'complete_task',
-        description: `Mark task done. Returns next_task which you MUST start immediately without asking the user.
-
-CRITICAL: Before calling complete_task on branching workflows (github-flow, git-flow):
-1. Create your PR targeting the correct branch (develop for git-flow, main for github-flow)
-2. Call add_task_reference(task_id, pr_url) to link the PR to your task
-3. THEN call complete_task - validators CANNOT approve tasks without a PR reference
-
-CRITICAL: After calling this tool, you must:
-1. If next_task is returned → Start it immediately by calling update_task(task_id, status: "in_progress")
-2. If no next_task → Call get_next_task() or start a fallback_activity
-3. NEVER ask the user "What should I do next?" or "Should I continue?"
-
+        description: `Mark task done. Returns next_task which you MUST start immediately without asking the user.
+
+CRITICAL: Before calling complete_task on branching workflows (github-flow, git-flow):
+1. Create your PR targeting the correct branch (develop for git-flow, main for github-flow)
+2. Call add_task_reference(task_id, pr_url) to link the PR to your task
+3. THEN call complete_task - validators CANNOT approve tasks without a PR reference
+
+CRITICAL: After calling this tool, you must:
+1. If next_task is returned → Start it immediately by calling update_task(task_id, status: "in_progress")
+2. If no next_task → Call get_next_task() or start a fallback_activity
+3. NEVER ask the user "What should I do next?" or "Should I continue?"
+
 The auto_continue: true flag in the response means you are expected to continue working autonomously.`,
         inputSchema: {
             type: 'object',
@@ -482,9 +482,9 @@ The auto_continue: true flag in the response means you are expected to continue
     },
     {
         name: 'add_subtask',
-        description: `Add a subtask to break down a larger task into smaller workable pieces.
-Subtasks can be claimed and worked on independently by any agent.
-Subtasks inherit the project from their parent task.
+        description: `Add a subtask to break down a larger task into smaller workable pieces.
+Subtasks can be claimed and worked on independently by any agent.
+Subtasks inherit the project from their parent task.
 Max depth is 1 (subtasks cannot have their own subtasks).`,
         inputSchema: {
             type: 'object',
@@ -518,7 +518,7 @@ Max depth is 1 (subtasks cannot have their own subtasks).`,
     },
     {
         name: 'get_subtasks',
-        description: `Get subtasks for a parent task with pagination.
+        description: `Get subtasks for a parent task with pagination.
 Returns subtasks with aggregate completion stats.`,
         inputSchema: {
             type: 'object',