Skip to main content
Glama

Morpha

by ai.morphareels
OverviewDiscussionsAdmin

Safe zones

safe_zones
Read-only

Return horizontal 'safe band' y-ranges of the canvas where a clip's burned-in video text (subtitles, lower thirds, titles) does NOT appear, plus the inverse 'text bands' (where it does). Reads the OCR cache built at clip-upload time (see detect_text_regions). Coordinates returned in BOTH source pixels and CANVAS pixels — canvas coords already account for the video layer's fit/anchor/position. Use to lay out captions, titles, callouts so they never collide with the video's own text. This is about the clip's own burned-in text: where TikTok and Instagram Reels cover the canvas with their UI is describe_video's platform_safe_area. Returns { ok: true, status: 'ready' | 'not-ready', data: { bands, safeBands, textBands } }.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
clipYesClip filename (video.<id>.clip).
projectIdYes
bandHeightNoVertical granularity in source pixels (default 32).
minConfidenceNoOCR confidence floor (0–100) for considering a text region (default 70).
occupancyThresholdNoFraction of frames that must contain text in a band to mark it occupied (default 0.10).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYesWhether the call succeeded.
dataNoThe payload, shaped by the tool.
noteNoWhat to do next when not ready.
errorNoWhy it failed.
statusNoFor cache-backed readers: whether the answer was ready.
editorUrlNoOpens this project in the editor.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • 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: -[
-  "projectId",
-  "clip",
-  "anonymousToken"
-]New value: +[
+  "projectId",
+  "clip"
+]
  2. Changed1 schema field changed
    • 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"
+}
  3. Changed2 schema fields changed
    • 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: -[
-  "projectId",
-  "clip"
-]New value: +[
+  "projectId",
+  "clip",
+  "anonymousToken"
+]
  4. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds meaningful behavioral context: it reads the OCR cache built at clip-upload time, returns coordinates in both source and canvas pixels with canvas coords already transformed for fit/anchor/position, and includes a status field ('ready' | 'not-ready') signaling possible unavailability. This goes beyond the annotation baseline.

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?

The description is information-dense but each sentence adds value: purpose, data source, coordinate system, usage, and distinction from a sibling. It is structured with the core function first, then details, then return format. Slightly long, but justified given the complexity and the need to disambiguate from similar tools.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers the purpose, data source, coordinate semantics, usage context, distinction from a related tool, and the return shape with status and data fields. The output schema is present (per context), and the description supplements it with band definitions. For a read-only analysis tool, nothing critical is missing for an agent to call it correctly.

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 80% (four of five parameters have descriptions). The schema already documents clip, bandHeight, minConfidence, and occupancyThreshold with clear meanings. The description does not add new parameter-level detail beyond what the schema provides, so it sits at the baseline 3 for high coverage. It does clarify the coordinate context for bandHeight (source pixels), but that is minor.

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+resource ('Return horizontal safe band y-ranges'), defines the exact scope (burned-in video text) and the inverse output (text bands). It explicitly distinguishes itself from describe_video's platform_safe_area and names the sibling detect_text_regions as the data source, so an agent can tell it apart from nearby tools without opening schemas.

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 gives a clear use case: 'Use to lay out captions, titles, callouts so they never collide with the video's own text.' It also names the alternative describe_video for platform UI safe areas, routing the agent correctly. It does not list explicit 'when not to use' conditions, but the contrast with describe_video is enough to guide selection.

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

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