MorphaReels

Add curve

add_curve

Draw an editable arrow / curved line — a stroked quadratic bezier with an arrowhead. Specify the two endpoints (x1,y1)→(x2,y2) in canvas pixels; bend pushes the midpoint perpendicular (px, 0 = straight line, positive/negative curves either way). color #rrggbb, stroke_width px, arrow_head none|end|both (default end). Use this for callout arrows (e.g. swooping into a link).

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": {
      "x1": "<x1>",
      "y1": "<y1>",
      "x2": "<x2>",
      "y2": "<y2>",
      "projectId": "<projectId>"
    },
    "name": "add_curve"
  }
}

Input Schema

Name	Required	Description
`x1`	Yes	Start x (canvas px).
`x2`	Yes	End x (canvas px) — the arrowhead end.
`y1`	Yes	Start y (canvas px).
`y2`	Yes	End y (canvas px).
`bend`	No	Perpendicular bow of the curve in px. 0 = straight.
`color`	No	Stroke colour as #rrggbb.
`projectId`	Yes	Opaque project id (a v4 UUID, from list_projects/create_project). Selects which existing project this call mutates.
`arrow_head`	No
`stroke_width`	No	Line thickness in px.

Output 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: -[
-  "x1",
-  "y1",
-  "x2",
-  "y2",
-  "projectId",
-  "anonymousToken"
-]New value: +[
+  "x1",
+  "y1",
+  "x2",
+  "y2",
+  "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: -[
-  "x1",
-  "y1",
-  "x2",
-  "y2",
-  "projectId"
-]New value: +[
+  "x1",
+  "y1",
+  "x2",
+  "y2",
+  "projectId",
+  "anonymousToken"
+]

First observedSep 7, 2026

TDQS

A4.2/5.0

Behavior3/5

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

Annotations (readOnlyHint=false, destructiveHint=false) already establish it as a non-destructive mutation. The description adds that the curve is 'editable' and explains arrowhead behavior, but it does not discuss side effects, reversibility, or interaction with existing content. Given annotation coverage, this is adequate but not extensive.

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, front-loaded with purpose and use case, then parameter details. No redundant or vague phrasing. 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?

The description covers endpoints, bend, color, stroke, arrowhead, and use case. The required projectId is described in the schema with context ('selects which existing project this call mutates'). An output schema exists (per context signals), so return format is not needed. It is reasonably complete for an add tool.

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?

With 89% schema coverage, the baseline is 3, but the description adds meaningful clarifications: 'bend pushes the midpoint perpendicular (px, 0 = straight line, positive/negative curves either way)' and the default for arrow_head ('none|end|both (default end)'). It also clarifies units ('canvas pixels'), going beyond the schema descriptions.

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 tool draws an editable arrow/curved line, a stroked quadratic bezier with arrowhead. It specifies the verb (draw), resource (arrow/curved line), and even a concrete use case ('callout arrows'), distinguishing it from siblings like add_shape or add_text_layer.

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?

It explicitly provides a when-to-use context: 'Use this for callout arrows (e.g. swooping into a link).' This gives clear guidance on when to apply the tool. However, it does not mention alternatives or when not to use it, which would elevate it to a 5.

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

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