Skip to main content
Glama

track_progress

Use this tool to log progress and update Memory Bank files via SSH, documenting actions like feature implementations or bug fixes with detailed descriptions.

Instructions

Track progress and update Memory Bank files

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesAction performed (e.g., 'Implemented feature', 'Fixed bug')
descriptionYesDetailed description of the progress
updateActiveContextNoWhether to update the active context file

Implementation Reference

  • Handler function that executes the track_progress tool by calling ProgressTracker.trackProgress and returning a response.
    export async function handleTrackProgress(
      progressTracker: ProgressTracker,
      action: string,
      description: string
    ) {
      await progressTracker.trackProgress(action, { description });
      return {
        content: [
          {
            type: 'text',
            text: `Progress tracked: ${action} - ${description}`,
          },
        ],
      };
    }
  • Input schema definition for the track_progress tool, including parameters for action and description.
    export const progressTools = [
      {
        name: 'track_progress',
        description: 'Track progress and update Memory Bank files',
        inputSchema: {
          type: 'object',
          properties: {
            action: {
              type: 'string',
              description: "Action performed (e.g., 'Implemented feature', 'Fixed bug')",
            },
            description: {
              type: 'string',
              description: 'Detailed description of the progress',
            },
            updateActiveContext: {
              type: 'boolean',
              description: 'Whether to update the active context file',
              default: true,
            },
          },
          required: ['action', 'description'],
        },
      },
    ];
  • Registration and dispatching of the track_progress tool in the main tool call handler switch statement.
    case 'track_progress': {
      const progressTracker = getProgressTracker();
      if (!progressTracker) {
        return {
          content: [
            {
              type: 'text',
              text: 'Memory Bank not found. Use initialize_memory_bank to create one.',
            },
          ],
          isError: true,
        };
      }
    
      const { action, description } = request.params.arguments as {
        action: string;
        description: string;
      };
      if (!action) {
        throw new McpError(ErrorCode.InvalidParams, 'Action not specified');
      }
      if (!description) {
        throw new McpError(ErrorCode.InvalidParams, 'Description not specified');
      }
      return handleTrackProgress(progressTracker, action, description);
    }
  • Core implementation of progress tracking, updating progress.md and active-context.md files in the Memory Bank.
    async trackProgress(action: string, details: ProgressDetails): Promise<string> {
      try {
        // Add GitHub profile URL to details if not already present
        if (!details.userId) {
          details.userId = this.userId;
        }
        
        // Update the progress file
        const updatedContent = await this.updateProgressFile(action, details);
        
        // Update the active context file
        await this.updateActiveContextFile(action, details);
        
        // Return the updated progress content
        return updatedContent;
      } catch (error) {
        console.error(`Error tracking progress: ${error}`);
        throw new Error(`Failed to track progress: ${error}`);
      }
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool updates Memory Bank files, implying a write/mutation operation, but doesn't specify what 'track progress' entails (e.g., creates new entries, appends to files, modifies existing data). It also lacks details on permissions, side effects, error handling, or response format, leaving significant gaps for a tool that modifies data.

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

Conciseness4/5

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

The description is a single, efficient sentence that front-loads the core purpose ('Track progress and update Memory Bank files'). It avoids redundancy and wastes no words, making it easy to parse quickly. However, it could be slightly more structured by explicitly separating the tracking and updating aspects for clarity.

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

Completeness2/5

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

Given the complexity of a progress-tracking tool with no annotations and no output schema, the description is incomplete. It doesn't explain what 'progress' means in this context, how updates affect Memory Bank files, what the tool returns, or any behavioral nuances. For a mutation tool with 3 parameters, this leaves too much unspecified for reliable agent use.

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 the schema already documents all parameters (action, description, updateActiveContext) with clear descriptions. The tool description adds no additional meaning beyond what's in the schema, such as explaining how parameters interact or their impact on Memory Bank files. With high schema coverage, the baseline is 3, as the description doesn't compensate but also doesn't detract.

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

Purpose3/5

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

The description 'Track progress and update Memory Bank files' states the general purpose but lacks specificity. It mentions tracking progress and updating files, but doesn't clarify what 'track progress' means operationally (e.g., logging, recording, documenting) or what specific Memory Bank files are involved. It distinguishes somewhat from siblings like 'log_decision' or 'write_memory_bank_file' by implying progress tracking, but the distinction is vague.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., requires an initialized memory bank), exclusions, or comparisons to siblings like 'log_decision', 'update_active_context', or 'write_memory_bank_file'. Without such context, an agent must infer usage from the tool name and parameters alone.

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/aakarsh-sasi/memory-bank-mcp'

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