Skip to main content
Glama

Coline

Set a task's parent

set_task_parent
DestructiveIdempotent

Makes a task a sub-task of another task on the same board, or detaches it with parentTaskId null.

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": {
      "workspace": "<workspace>",
      "taskboardId": "<taskboardId>",
      "taskId": "<taskId>",
      "parentTaskId": "<parentTaskId>"
    },
    "name": "set_task_parent"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskIdYesTask id from list_tasks, find_task or get_task.
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".
taskboardIdYesBoard id from list_boards.
parentTaskIdYes

Output Schema

NameRequiredDescriptionDefault
taskYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false; the description adds the useful 'same board' constraint and the null-means-detach behavior. It does not disclose the risky parts an agent would want: whether descendants are affected on detach, cycle prevention, or permission requirements for a destructive mutation.

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?

A single front-loaded sentence covering both the add-parent and remove-parent cases with no filler. Every clause earns its place.

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?

An output schema exists and annotations cover the safety profile, so the description only needs to pin down the operation and its constraints – which it mostly does, including the same-board rule and detach semantics. The gap on destructive side effects (what happens to existing sub-tasks) keeps it short of full completeness.

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?

Schema coverage is 75% and the one undocumented parameter is parentTaskId – the description supplies exactly that missing meaning by stating that null detaches the task. The other three parameters' semantics are already carried by schema descriptions pointing at list_tasks/list_boards/workspaces.

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 names a specific verb+resource ('Makes a task a sub-task of another task') and adds the inverse operation (detach via parentTaskId null), which cleanly distinguishes it from status/blocker-related siblings. It does not name an alternative tool, but the operation is unambiguous.

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?

Usage is implied by the operation itself (establish or remove a parent-child hierarchy), and the same-board constraint gives a boundary condition. However, there is no explicit when-not guidance, no mention of prerequisites such as listing relations first, and no pointer to siblings like list_task_relations.

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.

Resources