Skip to main content
Glama

Move task

move_task
DestructiveIdempotent

Move a task to a different billing project within your organization. Both the task and the destination project 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": {
      "task_id": "<task_id>",
      "new_project_id": "<new_project_id>"
    },
    "name": "move_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
task_idYesID of the task to move (required).
new_project_idYesID of the destination project (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.5/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 permission threshold (Admin or above) and the tenant-boundary constraint, which is genuine value. It does not explain the destructive consequences of the move — what happens to existing time entries, assignments, budget allocations, or approval state attached to the task — which is the key behavioural unknown for a destructive operation.

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?

Three short sentences, front-loaded with the action, followed by the two hard constraints. No filler and no repetition of the title.

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 destructive, permission-gated mutation with no output schema, the description covers who can call it and what invariants must hold. It leaves out the after-effects of the move and what the caller gets back, which the missing output schema means the description should have hinted at.

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 description coverage is 100%, so task_id, new_project_id and idempotency_key are already documented, including the org constraint on the destination. The description adds nothing beyond that baseline, though nothing is missing either.

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 (Move) and resource (task) plus the scope of the destination (a different billing project in the organization). It implicitly separates itself from move_project and move_subtask by naming 'task' as the object, but it never explicitly routes the agent away from those near siblings.

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?

Gives real preconditions: both the task and destination project must be in the organization and the caller needs Admin role or above. It stops short of saying when to use this versus move_subtask for a subtask or move_project for the parent project, so the choice between siblings is left implicit.

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