Skip to main content
Glama

update_progress

Track and update task progress on Buildable projects by providing task ID, progress percentage, status updates, completed steps, current step, challenges, modified files, time spent, and additional notes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
challengesNoAny challenges or blockers encountered
completed_stepsNoList of completed steps
current_stepNoCurrent step being worked on
files_modifiedNoList of files that were modified
notesNoAdditional notes
progressYesProgress percentage (0-100)
status_updateYesBrief status update message
task_idYesThe ID of the task being updated
time_spentNoTime spent in minutes

Implementation Reference

  • src/cli.ts:95-159 (registration)
    MCP tool registration for 'update_progress', including Zod input schema and handler that delegates to client.updateProgress
    this.server.tool(
      'update_progress',
      {
        task_id: z.string().describe('The ID of the task being updated'),
        progress: z
          .number()
          .min(0)
          .max(100)
          .describe('Progress percentage (0-100)'),
        status_update: z.string().describe('Brief status update message'),
        completed_steps: z
          .array(z.string())
          .optional()
          .describe('List of completed steps'),
        current_step: z
          .string()
          .optional()
          .describe('Current step being worked on'),
        challenges: z
          .array(z.string())
          .optional()
          .describe('Any challenges or blockers encountered'),
        files_modified: z
          .array(z.string())
          .optional()
          .describe('List of files that were modified'),
        time_spent: z.number().optional().describe('Time spent in minutes'),
        notes: z.string().optional().describe('Additional notes'),
      },
      async ({
        task_id,
        progress,
        status_update,
        completed_steps,
        current_step,
        challenges,
        files_modified,
        time_spent,
        notes,
      }) => {
        if (!this.client) {
          throw new Error('Not connected to Buildable API');
        }
    
        const result = await this.client.updateProgress(task_id, {
          progress,
          status_update,
          completed_steps,
          current_step,
          challenges,
          files_modified,
          time_spent,
          notes,
        });
    
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify(result, null, 2),
            },
          ],
        };
      }
    );
  • Core handler function that executes the progress update by making a POST request to the Buildable API endpoint /tasks/{taskId}/progress
    async updateProgress(
      taskId: string,
      progress: ProgressUpdate
    ): Promise<ProgressResponse> {
      this.log(
        'debug',
        `Updating progress for task ${taskId}: ${progress.progress}%`
      );
    
      try {
        const response = await this.makeRequest<ProgressResponse>(
          'POST',
          `/tasks/${taskId}/progress`,
          {
            completion_percentage: progress.progress,
            files_created: progress.files_modified,
            files_modified: progress.files_modified,
            notes: progress.notes,
            blockers: progress.challenges,
            time_spent_minutes: progress.time_spent,
            current_step: progress.current_step,
            completed_steps: progress.completed_steps,
          }
        );
    
        this.log('info', `Progress updated: ${progress.progress}% complete`);
    
        // Update connection activity
        await this.updateConnectionStatus('working', taskId);
    
        return response.data!;
      } catch (error) {
        this.log('error', `Failed to update progress for task ${taskId}:`, error);
        throw error;
      }
    }
  • Zod schema for input validation of the update_progress tool parameters
      task_id: z.string().describe('The ID of the task being updated'),
      progress: z
        .number()
        .min(0)
        .max(100)
        .describe('Progress percentage (0-100)'),
      status_update: z.string().describe('Brief status update message'),
      completed_steps: z
        .array(z.string())
        .optional()
        .describe('List of completed steps'),
      current_step: z
        .string()
        .optional()
        .describe('Current step being worked on'),
      challenges: z
        .array(z.string())
        .optional()
        .describe('Any challenges or blockers encountered'),
      files_modified: z
        .array(z.string())
        .optional()
        .describe('List of files that were modified'),
      time_spent: z.number().optional().describe('Time spent in minutes'),
      notes: z.string().optional().describe('Additional notes'),
    },
  • TypeScript interface defining the ProgressUpdate structure used by the updateProgress method and MCP tool
    export interface ProgressUpdate {
      progress: number; // 0-100
      status_update: string;
      completed_steps?: string[];
      current_step?: string;
      challenges?: string[];
      time_spent?: number; // minutes
      files_modified?: string[];
      notes?: string;
    }
  • Payload mapping from ProgressUpdate to API request body for the progress update endpoint
      completion_percentage: progress.progress,
      files_created: progress.files_modified,
      files_modified: progress.files_modified,
      notes: progress.notes,
      blockers: progress.challenges,
      time_spent_minutes: progress.time_spent,
      current_step: progress.current_step,
      completed_steps: progress.completed_steps,
    }
Behavior1/5

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

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

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

Completeness1/5

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

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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

Related 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/chunkydotdev/bldbl-mcp'

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