Skip to main content
Glama

Hang a task under another, or move it to a list

move
Idempotent

Reassign a task to a different list or nest it under a parent task; set part_of to null to make it standalone.

Instructions

part_of hangs a task under another, or null lets it stand alone; list moves it to a better list. One level: a task with parts is no part. A closed task takes nothing; a whole said done or not doing takes no new part.

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": "<task>"
    },
    "name": "move"
  }
}

Input Schema

NameRequiredDescriptionDefault
listNoAn existing list, by name, as `catch_up` names it
taskYesThe task id
part_ofNoId of the task to hang it under, or null to let it go

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.47.0
    • changedInput schema / properties / list / description
      Previous value: -"An existing list, by name (`lists`), for a task an agent filed"New value: +"An existing list, by name, as `catch_up` names it"
  2. Changed2 schema fields changedv1.43.2
    • changedInput schema / properties / list / description
      Previous value: -"An existing list, by name, for a task an agent filed; `lists` says which"New value: +"An existing list, by name (`lists`), for a task an agent filed"
    • changedInput schema / properties / part_of / description
      Previous value: -"The id of the task to hang it under, or null to let it go from the one it is a part of"New value: +"Id of the task to hang it under, or null to let it go"
  3. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare mutation (readOnlyHint=false), idempotence, and non-destructiveness. The description adds valuable constraint knowledge (single-level nesting, closed/done tasks reject parents), but it omits the notable behavior that passing null for `part_of` detaches an existing parent — a mutation effect an agent should know about, and it does not describe error behavior when a precondition is violated.

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

Conciseness3/5

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

Very short and front-loaded on the main parameter, but the telegraphic phrasing ('One level: a task with parts is no part', 'A whole said done or not doing takes no new part') costs clarity for the sake of brevity. Every sentence is relevant, yet the compression makes constraints harder to parse than plain prose would.

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 3-parameter mutation tool with annotations and no output schema, the definition covers the core constraints but leaves gaps: the interaction between `list` and `part_of`, the effect of null on an already-parented task, and failure modes. Adequate but not fully self-sufficient.

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 restates what the schema already says (`part_of` null lets it go) and clarifies that `list` takes a list by name, but it adds nothing about the `task` parameter and does not resolve whether `list` and `part_of` may be used in the same call.

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?

The description states specific verbs and resources: `part_of` hangs a task under another (or detaches with null), and `list` moves the task to another list. The title reinforces this, and the operation is clearly a reparenting/relisting mutation, though no sibling is named as an alternative to distinguish it from e.g. `reschedule` or `say_done`.

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?

It gives real preconditions: only one level of nesting (a task with parts cannot be a part), a closed task accepts nothing, and a task marked done or not-doing cannot take a new part. What is missing is routing guidance — it never says when to prefer this over other task-modifying siblings, or whether `list` and `part_of` can be supplied together.

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