lxDIG MCP

task_update

Update the status of a tracked task using task ID and new status (e.g., completed, blocked). Add optional notes, assignee, or due date to keep delivery state current.

Instructions

Update the status of a tracked task. Requires taskId (from progress_query results) and status (new status string, e.g. completed, blocked, in-progress). Optional: notes (progress notes or blockers), assignee, dueDate. Use after completing or blocking a task to keep delivery state current.

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": {
      "taskId": "<taskId>",
      "status": "<status>"
    },
    "name": "task_update"
  }
}

Input Schema

Name	Required	Description	Default
`taskId`	Yes	Task ID
`status`	Yes	New status
`notes`	No	Optional notes
`assignee`	No	Task assignee
`dueDate`	No	Task due date
`agentId`	No	Agent identifier
`profile`	No	Response profile	compact

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Jun 21, 2026

TDQS

A3.6/5.0

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 only states that the tool updates status and optional fields, but does not disclose side effects, idempotency, permissions, rate limits, or response behavior. This is insufficient for a mutation tool.

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 two sentences, front-loading the verb and resource, then detailing requirements and optional fields. No superfluous content, earning its place efficiently.

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?

The tool has 7 parameters and no output schema, but the description fails to explain return values, error handling, or validation behavior. This is a significant gap for a mutation tool, leaving the agent underinformed about what to expect after invocation.

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 coverage is 100%, so baseline is 3. The description adds some semantic value by specifying that taskId comes from progress_query results, providing status examples, and clarifying notes as progress notes/blockers. However, it does not deeply elaborate parameter usage beyond the schema.

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 clearly states 'Update the status of a tracked task,' specifying the verb (update) and resource (task). It distinguishes from sibling tools like progress_query (query only) and agent_status (agent status), making the purpose unambiguous.

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 advises using the tool after completing or blocking a task to keep delivery state current, which provides clear when-to-use guidance. It also notes that taskId comes from progress_query results. However, it does not explicitly mention when not to use or alternatives.

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