Skip to main content
Glama

change_task_status

Update task progress by moving it to a different stage within a FluentBoards project management board.

Instructions

Change the status/stage of a task

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
board_idYesBoard ID
task_idYesTask ID
stage_idYesNew stage ID

Implementation Reference

  • Handler function that executes the tool logic: destructures args, makes a PUT request to update the task's stage_id via the API, and formats the response.
    async (args) => {
      const { board_id, task_id, stage_id } = args;
    
      const response = await api.put(`/projects/${board_id}/tasks/${task_id}`, {
        property: 'stage_id',
        value: stage_id,
      });
      return formatResponse(response.data);
    }
  • Zod schema defining the input parameters: board_id, task_id, and stage_id, all positive integers.
    {
      board_id: z.number().int().positive().describe("Board ID"),
      task_id: z.number().int().positive().describe("Task ID"),
      stage_id: z.number().int().positive().describe("New stage ID"),
    },
  • Registers the change_task_status tool on the MCP server using server.tool, providing name, description, input schema, and handler function.
    server.tool(
      "change_task_status",
      "Change the status/stage of a task",
      {
        board_id: z.number().int().positive().describe("Board ID"),
        task_id: z.number().int().positive().describe("Task ID"),
        stage_id: z.number().int().positive().describe("New stage ID"),
      },
      async (args) => {
        const { board_id, task_id, stage_id } = args;
    
        const response = await api.put(`/projects/${board_id}/tasks/${task_id}`, {
          property: 'stage_id',
          value: stage_id,
        });
        return formatResponse(response.data);
      }
    );
  • src/index.ts:23-23 (registration)
    Top-level registration call that invokes registerTaskTools on the main MCP server instance, thereby registering the change_task_status tool among others.
    registerTaskTools(server);
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It indicates a mutation ('Change') but doesn't address permissions, side effects, error handling, or response format. This is inadequate for a tool that modifies task states, as critical behavioral traits like reversibility or impact are omitted.

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 with zero waste—it directly states the tool's function without fluff. It's appropriately sized for a simple tool and front-loaded with the core action, 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?

For a mutation tool with no annotations and no output schema, the description is insufficient. It lacks details on behavioral traits, usage context, and return values, leaving gaps that could hinder an agent's ability to invoke it correctly or handle outcomes. The high schema coverage doesn't compensate for these missing elements.

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 fully documents parameters (board_id, task_id, stage_id). The description adds no additional meaning beyond implying these are used to change task status, which aligns with the schema but doesn't provide extra context like valid stage IDs or relationships between parameters.

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 action ('Change') and resource ('status/stage of a task'), making the purpose understandable. It doesn't explicitly distinguish from sibling tools like 'update_task' which might handle broader task modifications, but it's specific enough to convey its focused function.

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?

No guidance is provided on when to use this tool versus alternatives like 'update_task' or 'create_stage'. The description implies usage for status changes but doesn't specify prerequisites, exclusions, or contextual triggers, leaving the agent to infer based on tool names 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

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/danieliser/fluent-boards-mcp-server'

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