Skip to main content
Glama

Move subtask

move_subtask
DestructiveIdempotent

Move a subtask to a different task within your organization. Both the subtask and the destination task must belong to your organization. Requires Admin role or above.

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": {
      "subtask_id": "<subtask_id>",
      "new_task_id": "<new_task_id>"
    },
    "name": "move_subtask"
  }
}

Input Schema

NameRequiredDescriptionDefault
subtask_idYesID of the subtask to move (required).
new_task_idYesID of the destination task (required, must belong to your organization).
idempotency_keyNoOptional caller-supplied key; retrying with the same key returns the original result instead of acting twice.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered; the description adds genuinely new facts beyond that — the Admin-role requirement and the cross-organization restriction on both the subtask and destination. It still doesn't say that the subtask is detached from its original task or what happens to its time entries or assignments, which would be the most valuable mutation detail.

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?

Three short sentences, front-loaded with the action and scoping rule. There is slight redundancy between 'within your organization' and 'both the subtask and the destination task must belong to your organization', but nothing is wasteful enough to impede reading.

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 three-parameter mutation with full schema documentation, rich annotations, and no output schema, the definition covers scope, permission requirement, and idempotency sufficiently for correct invocation. The remaining gap is side-effect disclosure about the subtask's prior parentage and attached data.

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 subtask_id, new_task_id, and idempotency_key are all documented, including the org constraint on the destination. The description adds no syntax, format, or edge-case meaning beyond what the schema states, which is the expected baseline here.

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 gives a specific verb and resource ('Move a subtask to a different task'), which clearly separates it from move_project and move_task by the object being relocated. It stops short of naming those siblings as alternatives, so differentiation is implied by resource rather than stated.

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?

It supplies meaningful preconditions for invocation: both objects must be in the caller's organization and the caller needs Admin role or above. However, it never addresses when to use this versus move_task or how to handle a subtask that should instead be recreated, leaving the selection guidance implied rather than explicit.

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