mFlow

reorder_standalone_tasks

Set the complete drag-and-drop order for one status column. taskIds is the full ordered list of tasks that should end up with the given status — this replaces the whole column's order (and moves in any task not already on that status), it does not reposition a single task relative to its neighbors.

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": {
      "projectId": "<projectId>",
      "status": "<status>",
      "taskIds": "<taskIds>"
    },
    "name": "reorder_standalone_tasks"
  }
}

Input Schema

Name	Required	Description
`status`	Yes	The status id (column) being reordered — every task in taskIds ends up with this status.
`taskIds`	Yes	The complete, ordered list of task ids for this status column after the reorder.
`projectId`	Yes	The project the column belongs to.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedSep 18, 2026

addedInput schema / properties / projectId / description
```
Added value: +"The project the column belongs to."
```

addedInput schema / properties / status / description

Added value: +"The status id (column) being reordered — every task in taskIds ends up with this status."

addedInput schema / properties / taskIds / description

Added value: +"The complete, ordered list of task ids for this status column after the reorder."

First observedSep 18, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already indicate this is a mutating operation (readOnlyHint=false) and not destructive (destructiveHint=false). The description adds valuable context beyond this by stating that the tool replaces the entire column order and 'moves in any task not already on that status,' clarifying the scope of mutation. It does not mention auth requirements or rate limits, but these are not critical for a reorder 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?

Two sentences with no wasted words. The main purpose is front-loaded, followed by a clear semantic clarification and a note about what it does not do. Every sentence 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?

Given no output schema and three parameters, the description covers the essential behavior, including the 'replace entire column' semantic and the movement of tasks into the status. A minor gap is that it doesn't explicitly state what happens to tasks currently on the status that are not in taskIds, but the description implies they will no longer have that status. This is adequate for an agent to call the tool correctly.

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 100%, so the baseline is 3. The description adds meaning by clarifying that taskIds is 'the full ordered list of tasks that should end up with the given status' and that the operation replaces the whole column order, which is more specific than the schema's description. It also clarifies the status parameter's role.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the specific action ('Set the complete drag-and-drop order for one status column') and identifies the resource ('one status column'). It distinguishes itself from sibling tools like reorder_standalone_statuses (which reorders columns) and update_standalone_task (which updates task fields) by emphasizing the 'complete' ordering scope.

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?

The description provides clear context for when to use it: when setting the entire order of a status column, and explicitly contrasts it with single-task repositioning ('it does not reposition a single task relative to its neighbors'). However, it does not name specific sibling tools or provide exhaustive when-not-to-use conditions, so it falls short of a 5.

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

All mFlow tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?