Skip to main content
Glama

Update Task

update_task
DestructiveIdempotent

Update a task you own: title, status, priority, assignee, description, due date, or add/remove typed document/note/memory links. Pass body to replace the Markdown description. Pass due_at (ISO 8601) to set it or null to clear it. A done or cancelled task is terminal — it can only be reopened to "open". An agent credential can close (done/cancelled) a task only if it created that task, or if it is the task's assignee — an agent assigned to a task, including one a person created, can complete it itself; an agent that neither created nor is assigned to a task needs the assignee or a person to close it. Pass note with status to say why (up to 300 characters). For blocked or human_review, say what you need from a person: Gryz sends no notification, and they see it when they open Tasks. In your own Gryz, send the same status with a new note to replace the reason. Every status change is recorded in the task's audit trail.

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": "update_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
bodyNoReplace the task's Markdown description/body.
noteNoGoes with `status`: a short note on the change. For blocked or human_review, say what you need from a person; they see it on their Tasks page. In your own Gryz, send the same status with a new note to replace a reason. Up to 300 characters.
titleNoRename the task.
due_atNoISO 8601 due date/time, or null to clear it.
statusNo
assigneeNo
priorityNo
add_linksNo
remove_linksNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations only say destructive/idempotent/non-read-only; the description adds the real behavior an agent needs — done/cancelled are terminal and only reopenable to open, agent credentials can close only tasks they created or are assigned to, and every status change lands in the audit trail. It also discloses that Gryz sends no notification, so the human only sees the reason when they open Tasks.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the field list, then permissions and terminal-state rules in a logical order. Slight redundancy: the note-as-reason guidance appears twice ('Pass `note` with `status` to say why' and 'send the same status with a new note to replace the reason'), which could be merged.

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?

For a 10-parameter mutation tool with no output schema, the description covers the hard parts — terminal states, credential-based close permissions, note semantics, audit trail. It omits what a successful call returns and how link roles affect anything, but nothing needed to call it safely is missing.

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

Parameters4/5

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

With 40% schema coverage the description does real work: body replaces (not appends to) the Markdown description, due_at is ISO 8601 or null to clear, and note pairs with status and carries a reason. Gaps remain for assignee, priority, and add_links/remove_links (kind and role values are unexplained), and the stated 300-character note limit conflicts with the schema maxLength of 1200.

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 a task you own') and enumerates exactly which fields can change (title, status, priority, assignee, description, due date, links). An agent can distinguish this from create_task or get_task without opening the schema.

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?

Gives concrete when-to-use rules: note accompanies status to explain a change; note is mandatory-in-spirit for blocked/human_review; a new note replaces the reason. It never names a sibling alternative explicitly, which keeps it short of a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.