Skip to main content
Glama

bmad_update_task_status

Update task status in CastPlan MCP to track progress through pending, assigned, in-progress, needs-revision, or completed states.

Instructions

Update the status of a specific task

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
taskIdYesID of the task to update
statusYesNew status for the task

Implementation Reference

  • The MCP tool handler function for 'bmad_update_task_status'. It extracts taskId and status from args, calls the BMADService to update the task status, and returns a success response with the details.
    tools.set('bmad_update_task_status', async (args: any) => {
      const updated = await bmadService.updateTaskStatus(args.taskId, args.status);
      return { success: updated, taskId: args.taskId, status: args.status };
    });
  • The input schema definition for the 'bmad_update_task_status' tool, specifying required taskId (string) and status (enum of possible task statuses).
    {
      name: 'bmad_update_task_status',
      description: 'Update the status of a specific task',
      inputSchema: {
        type: 'object',
        properties: {
          taskId: {
            type: 'string',
            description: 'ID of the task to update'
          },
          status: {
            type: 'string',
            enum: ['pending', 'assigned', 'in-progress', 'needs-revision', 'completed'],
            description: 'New status for the task'
          }
        },
        required: ['taskId', 'status']
      }
    }
  • src/index.ts:405-407 (registration)
    Registration of BMAD tools (including 'bmad_update_task_status') in the main server by calling registerBMADTools with the tools Map and BMADService instance, then adding definitions to toolDefinitions.
    if (this.config.services.bmad && this.bmadService) {
      const bmadTools = registerBMADTools(this.tools, this.bmadService);
      this.toolDefinitions.push(...bmadTools);
  • BMADService helper method that finds a task by ID in the internal tasks array, updates its status and updatedAt timestamp if found, and returns boolean success.
    async updateTaskStatus(taskId: string, status: Task['status']): Promise<boolean> {
      const task = this.tasks.find(t => t.id === taskId);
      if (task) {
        task.status = status;
        task.updatedAt = new Date().toISOString();
        return true;
      }
      return false;
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states 'Update' implies a mutation, but doesn't cover permissions, side effects, error handling, or response format. For a mutation tool with zero annotation coverage, this is inadequate, as it leaves critical behavioral aspects unspecified.

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 a single, efficient sentence that directly states the tool's purpose without any wasted words. It's appropriately sized and front-loaded, making it easy to parse quickly.

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 tool is a mutation (updating task status) with no annotations and no output schema, the description is incomplete. It doesn't explain what happens on success or failure, any constraints on status transitions, or how it integrates with sibling tools like 'track_document_work'. For a 2-parameter mutation tool, more context is needed.

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?

The description doesn't add meaning beyond the input schema, which has 100% coverage with clear descriptions and an enum for 'status'. Since schema_description_coverage is high, the baseline is 3, as the schema adequately documents the parameters without needing extra explanation in the description.

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

Purpose4/5

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

The description clearly states the verb ('Update') and resource ('status of a specific task'), making the purpose immediately understandable. However, it doesn't differentiate this tool from potential sibling tools that might also update task properties, like 'track_document_work' or 'update_document_lifecycle', which could involve task status changes in some contexts.

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, context, or exclusions, such as whether the task must exist or be in a certain state. Given the sibling tools include 'track_document_work' and 'update_document_lifecycle', which might overlap with task management, this lack of differentiation is a significant gap.

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/Ghostseller/CastPlan_mcp'

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