Vibe Board VE

board_update_task

Update a task's status, assignment, priority, RIPER mode, or project. Move tasks between projects while preserving subtask relationships manually.

Instructions

Update a task's status, assignment, priority, RIPER mode, project, or other fields. Pass project_id to move the task to a different project (the target project must exist; subtasks are NOT auto-moved — caller must move them separately if needed).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "task_id": "<task_id>"
    },
    "name": "board_update_task"
  }
}

Input Schema

Name	Required	Description
`task_id`	Yes	Task ID to update
`status`	No	New status
`priority`	No	New priority
`assigned_agent`	No	New agent assignment (empty string to unassign)
`riper_mode`	No	New RIPER mode
`title`	No	Updated title
`description`	No	Updated description
`depends_on`	No	Updated dependency list
`metadata`	No	Metadata to merge
`project_id`	No	Move task to this project. Target project must exist. Subtasks are NOT auto-moved — their parent_task_id link will cross projects unless the caller also moves them. Returns a warning in the message if the task has subtasks still in the source project.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Apr 19, 2026

TDQS

A4.2/5.0

Behavior4/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 discloses that moving a task to a different project requires the target project to exist and that subtasks are not automatically moved, which is a critical behavioral detail. However, it doesn't mention other side effects like idempotency or auth requirements.

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 extremely concise, consisting of two sentences that front-load the main purpose and immediately follow with the key behavioral caveat. Every sentence adds value with no redundancy.

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

Completeness4/5

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

Given the complexity (10 parameters including nested objects) and no output schema, the description covers the primary purpose and a critical behavioral detail. However, it does not explain the return value or error conditions, which would be helpful but are not required since no output schema exists.

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 input schema has 100% description coverage, so the baseline is 3. The description adds value by explaining the project_id parameter's behavior (subtask handling warning). Other parameters are self-explanatory from the schema descriptions, so no significant additional meaning is needed.

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

Purpose5/5

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

The description explicitly states it updates a task's status, assignment, priority, RIPER mode, project, or other fields, distinguishing it from sibling tools like board_create_task or board_delete_task. It uses specific verbs and resources.

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

Usage Guidelines4/5

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

The description clearly indicates when to use the tool (to update various task fields) and includes a specific warning about moving tasks between projects and the need to handle subtasks separately. While it does not explicitly list alternatives, it provides sufficient context for usage decisions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server