Skip to main content
Glama

task_update

Updates a user task's metadata—name, description, assignee, due date, priority, or parent task—without advancing it in the workflow. Use it to correct or reassign task details.

Instructions

Update metadata of a user task: name, description, assignee, due date, priority, or parent task. Does not advance the task in the workflow.

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

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.3.0
    • addedInput schema / additionalProperties
      Added value: +{}
    • addedInput schema / properties / id
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / required
      Added value: +[
      +  "id"
      +]
  2. First observedv1.1.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It usefully discloses the non-advancing nature of the mutation, but omits permission requirements, whether omitted fields are left untouched, whether values are overwritten wholesale, and what the response contains.

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?

Two tight sentences with the field list up front and the exclusion immediately after; there is no filler and nothing an agent must read past to reach the key constraint.

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

Completeness3/5

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

For a single-required-param tool with an open schema this is a reasonable outline, and the absence of an output schema removes the need to describe returns. Still, the open additionalProperties means the field list is the de facto contract, and it lacks the value formats and null/partial-update semantics the agent would need to call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the schema exposes only an untyped "id" plus additionalProperties, so the description is the sole source of parameter meaning. It lists six updatable fields but gives no value formats for any of them — due date format, priority scale, and whether assignee is a user ID or name are all left undefined.

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?

States a specific verb and resource ("Update metadata of a user task") and enumerates the updatable attributes, so the agent knows exactly what is being changed. The closing clause distinguishes it from workflow-advancing siblings such as task_complete or task_resolve.

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 negative constraint "Does not advance the task in the workflow" implicitly routes the agent away from this tool when a status transition is needed. However, no sibling is named and no positive trigger conditions or prerequisites are stated, so the agent must infer which alternative to pick.

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

Deploy Server

Other Tools