Skip to main content
Glama

open_motif_draft

Open an editable draft from a live folder, existing Motif, independent copy, or blank canvas, then return its motif ID and revision for continued editing.

Instructions

Open a draft; returns {motif_id, revision}. directory: a live linked folder (reopening returns its draft). motif: a draft id resumes that draft, any other id copies it. copy: an independent copy of any Motif, drafts included. Copies answer source {id, version}. empty: 960×540, 5 s, no props.

Input Schema

NameRequiredDescriptionDefault
sourceYesExactly one source variant.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.6.0
    • changedInput schema / properties / source / oneOf
      Previous value: -[
      -  {
      -    "additionalProperties": false,
      -    "properties": {
      -      "kind": {
      -        "const": "directory",
      -        "description": "Source type."
      -      },
      -      "path": {
      -        "description": "Absolute package directory on the app machine.",
      -        "type": "string"
      -      }
      -    },
      -    "required": [
      -      "kind",
      -      "path"
      -    ],
      -    "type": "object"
      -  },
      -  {
      -    "additionalProperties": false,
      -    "properties": {
      -      "kind": {
      -        "const": "zip",
      -        "description": "Source type."
      -      },
      -      "path": {
      -        "description": "Absolute path on the app machine.",
      -        "type": "string"
      -      }
      -    },
      -    "required": [
      -      "kind",
      -      "path"
      -    ],
      -    "type": "object"
      -  },
      -  {
      -    "additionalProperties": false,
      -    "properties": {
      -      "file_id": {
      -        "description": "Temporary file transfer id.",
      -        "type": "string"
      -      },
      -      "kind": {
      -        "const": "zip",
      -        "description": "Source type."
      -      }
      -    },
      -    "required": [
      -      "kind",
      -      "file_id"
      -    ],
      -    "type": "object"
      -  },
      -  {
      -    "additionalProperties": false,
      -    "properties": {
      -      "id": {
      -        "description": "Motif id.",
      -        "type": "string"
      -      },
      -      "kind": {
      -        "const": "motif",
      -        "description": "Source type."
      -      }
      -    },
      -    "required": [
      -      "kind",
      -      "id"
      -    ],
      -    "type": "object"
      -  },
      -  {
      -    "additionalProperties": false,
      -    "properties": {
      -      "kind": {
      -        "const": "empty",
      -        "description": "Source type."
      -      },
      -      "name": {
      -        "description": "Initial display name.",
      -        "type": "string"
      -      }
      -    },
      -    "required": [
      -      "kind"
      -    ],
      -    "type": "object"
      -  }
      -]New value: +[
      +  {
      +    "additionalProperties": false,
      +    "properties": {
      +      "kind": {
      +        "const": "directory",
      +        "description": "Source type."
      +      },
      +      "path": {
      +        "description": "Absolute package directory on the app machine.",
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "kind",
      +      "path"
      +    ],
      +    "type": "object"
      +  },
      +  {
      +    "additionalProperties": false,
      +    "properties": {
      +      "kind": {
      +        "const": "zip",
      +        "description": "Source type."
      +      },
      +      "path": {
      +        "description": "Absolute path on the app machine.",
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "kind",
      +      "path"
      +    ],
      +    "type": "object"
      +  },
      +  {
      +    "additionalProperties": false,
      +    "properties": {
      +      "kind": {
      +        "const": "motif",
      +        "description": "Source type."
      +      },
      +      "motif_id": {
      +        "description": "Motif id (list_motifs).",
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "kind",
      +      "motif_id"
      +    ],
      +    "type": "object"
      +  },
      +  {
      +    "additionalProperties": false,
      +    "properties": {
      +      "kind": {
      +        "const": "copy",
      +        "description": "Source type."
      +      },
      +      "motif_id": {
      +        "description": "Motif id (list_motifs).",
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "kind",
      +      "motif_id"
      +    ],
      +    "type": "object"
      +  },
      +  {
      +    "additionalProperties": false,
      +    "properties": {
      +      "kind": {
      +        "const": "empty",
      +        "description": "Source type."
      +      },
      +      "name": {
      +        "description": "Display name; the draft's first publication takes its id from it.",
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "kind"
      +    ],
      +    "type": "object"
      +  }
      +]
  2. Addedv0.4.0

TDQS

A4/5.0
Behavior4/5

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

Annotations only declare openWorldHint=false and destructiveHint=false, so the description carries real weight here and delivers: the return shape {motif_id, revision}, idempotent reopening of a directory draft, resume-vs-copy behavior for motif ids, and the fact that copies report their source {id, version}. It stops short of stating persistence/locking behavior (e.g., what happens if a draft is already open elsewhere).

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?

Front-loaded with the action and return shape, then one compact line per source variant with no filler. The telegraphic register ("Copies answer source {id, version}") is dense enough that an agent may need a second read, but nothing is redundant.

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 single nested oneOf parameter with no output schema, the description covers four of five variants plus the returned {motif_id, revision}, which is a lot of the needed surface. The omission of the 'zip' source kind is the notable gap, since that path format and its consequences are documented nowhere else.

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, but the description genuinely adds meaning the schema lacks: the schema labels both 'motif' and 'copy' entries identically as "Motif id (list_motifs)", and only the description distinguishes resume from duplicate. The 'empty' defaults (960×540, 5 s, no props) are also absent from the schema. The 'zip' variant is left entirely unexplained, which keeps this from a 5.

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?

"Open a draft" gives a specific verb plus resource, and the per-variant lines make clear this tool materializes a draft from one of several sources. It never names a sibling (read_motif, preview_motif, install_motif, open_project), so the agent must infer the boundary with those tools from names alone.

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 effectively routes the agent across variants: directory = live linked folder, motif = resume if draft id else copy, copy = independent duplicate, empty = blank 960×540 5 s project. It gives clear usage context for each mode but no explicit exclusions relative to sibling motif tools or guidance on which tool to pick when a Motif merely needs inspection.

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

Deploy Server

Other Tools