Skip to main content
Glama

ui_move_task

Reparent or reorder a task within a project by assigning a new parent and sort position.

Instructions

App-only: reparent or reorder a task.

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": {
      "project_id": "<project_id>",
      "task_id": "<task_id>"
    },
    "name": "ui_move_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
task_idYes
sort_keyNo
project_idYes
new_parent_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden and largely fails to. For a mutation it does not say what happens when new_parent_id is null (detach to root?), what happens if sort_key is omitted, whether the move can fail on cycles or permission checks, or what the response contains. Only the vague 'App-only' restriction counts as added context.

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?

A single front-loaded clause with zero filler, and the app-scope caveat precedes the action. It is concise, though the brevity tips into under-specification rather than efficient communication.

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?

A four-parameter mutation with no annotations, no output schema, and no parameter documentation needs far more than nine words. Missing are mutation side effects, null-handling semantics, error modes, and the relationship between project_id, new_parent_id, and sort_key.

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%, so the description must compensate and it adds nothing about any of the four parameters. An agent must infer that new_parent_id null means no parent, that sort_key positions the task among siblings, and whether project_id is the destination project or the current one — all left ambiguous.

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?

Names a specific verb pair ('reparent or reorder') and a specific resource ('task'), which distinguishes it from the generic ui_update_task sibling. It falls short of 5 only because 'App-only' is left unexplained and the two operations (changing parent vs. changing sort position) are not tied to their parameters.

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

Usage Guidelines3/5

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

'App-only' signals a usage constraint, i.e., callable only from the app context, which is real but unelaborated guidance. There is no statement of when to pick this over ui_update_task (which could plausibly also change parent or ordering) and no exclusion conditions.

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