Morpha

Reorder pages

reorder_pages

Destructive

Move a page from from_index to to_index. The remaining pages shift to fill the gap; active_index is rewritten so it keeps pointing at the same page it did before the move. Fails on out-of-range indices.

Input Schema

TableJSON Schema

Name	Required	Description
`to_index`	Yes	0-based destination index for the page.
`projectId`	Yes	Opaque project id (a v4 UUID, from list_projects/create_project). Selects which existing project this call mutates.
`from_index`	Yes	0-based index of the page to move.

Output Schema

TableJSON Schema

Name	Required	Description
`ok`	Yes	Whether the call succeeded.
`data`	No	The payload, shaped by the tool.
`note`	No	What to do next when not ready.
`error`	No	Why it failed.
`status`	No	For cache-backed readers: whether the answer was ready.
`editorUrl`	No	Opens this project in the editor.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 17, 2026

removedInput schema / properties / anonymousToken

Removed value: -{
-  "description": "The token create_anonymous_account returned. This connection has no Morpha key, so every call carries it.",
-  "type": "string"
-}

changedInput schema / required

Previous value: -[
-  "from_index",
-  "to_index",
-  "projectId",
-  "anonymousToken"
-]New value: +[
+  "from_index",
+  "to_index",
+  "projectId"
+]

Changed1 schema field changedSep 15, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "description": "The result envelope every Morpha tool returns.",
+  "properties": {
+    "data": {
+      "description": "The payload, shaped by the tool.",
+      "type": [
+        "object",
+        "array",
+        "string",
+        "number",
+        "boolean",
+        "null"
+      ]
+    },
+    "editorUrl": {
+      "description": "Opens this project in the editor.",
+      "type": "string"
+    },
+    "error": {
+      "description": "Why it failed.",
+      "type": "string"
+    },
+    "note": {
+      "description": "What to do next when not ready.",
+      "type": "string"
+    },
+    "ok": {
+      "description": "Whether the call succeeded.",
+      "type": "boolean"
+    },
+    "status": {
+      "description": "For cache-backed readers: whether the answer was ready.",
+      "enum": [
+        "ready",
+        "not-ready"
+      ],
+      "type": "string"
+    }
+  },
+  "required": [
+    "ok"
+  ],
+  "type": "object"
+}

Changed2 schema fields changedSep 11, 2026

addedInput schema / properties / anonymousToken

Added value: +{
+  "description": "The token create_anonymous_account returned. This connection has no Morpha key, so every call carries it.",
+  "type": "string"
+}

changedInput schema / required

Previous value: -[
-  "from_index",
-  "to_index",
-  "projectId"
-]New value: +[
+  "from_index",
+  "to_index",
+  "projectId",
+  "anonymousToken"
+]

First observedSep 7, 2026

TDQS

A4.2/5.0

Behavior5/5

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

The description goes well beyond the annotations (destructiveHint=true, readOnlyHint=false) by disclosing precise side effects: remaining pages shift to fill the gap, active_index is rewritten to keep pointing at the same page, and out-of-range indices cause failure. This is exactly the behavioral context an agent needs before invoking 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?

Three sentences, each carrying distinct information: the core operation, the side-effect mechanics, and the failure mode. Front-loaded with the verb+operation and no filler or repetition of the schema.

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 3-parameter destructive mutation with a full output schema and complete annotations, the description covers the operation, side effects, and error behavior. Minor gaps remain (behavior when from_index equals to_index, exact bounds of 'out-of-range') but nothing an agent needs to invoke it correctly is missing.

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 the baseline is 3. The description adds the out-of-range failure condition and frames from_index/to_index as a move relationship, but the schema already documents each parameter clearly (0-based indices, projectId provenance). The contribution is marginal but not zero.

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 opens with a specific verb and resource ('Move a page from...') and names the exact index parameters involved. The operation is unambiguously about reordering pages within a project, which distinguishes it from siblings like reorder_layer, add_page, delete_page, and select_page without any ambiguity.

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?

The behavioral detail (pages shift to fill the gap, active_index preserved, fails on out-of-range) implicitly tells an agent when this tool is appropriate, but no alternative tools are named and no when-not conditions are given. With several close siblings (reorder_layer, move_layer, move_band), explicit routing guidance would meaningfully help an agent choose correctly.

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

All Morpha 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?