Skip to main content
Glama
Stellify-Software-Ltd

Stellify MCP Server

Official

create_file

Create an empty file shell for Laravel/Vue projects, returning a file UUID. Supports PHP classes, models, controllers, and Vue components with automatic dependency resolution and module grouping.

Instructions

Create an empty file shell in a Stellify project. Returns file UUID.

For PHP: type='class', 'model', 'controller', or 'middleware'. For Vue: type='js', extension='vue'. Auto-creates app.js and template route.

Pass 'includes' array for framework class dependencies (auto-resolved to UUIDs). Use 'models' array in save_file for project models.

IMPORTANT - Check appJs response for Vue components:

  • If appJs.action_required === "create_or_select_mount_file": No mount file exists. You MUST ask the user if they want to create a new app.js mount file before proceeding.

  • If appJs.action_required === "register_component": Mount file exists but component isn't registered. Call save_file on the mount file to add the component UUID to its includes array.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
directoryYesThe UUID of the directory to create the file in (get from get_project directories array)
nameYesFile name without extension (e.g., "Counter", "UserController")
typeYesType of file: "js" for JavaScript/Vue, others for PHP
extensionNoFile extension. Use "vue" for Vue components, omit for PHP files.
namespaceNoPHP namespace (e.g., "App\Services\"). Only for PHP files.
includesNoArray of namespace strings to include as dependencies (e.g., ["App\Models\User", "Illuminate\Support\Facades\Hash"]). These are resolved to UUIDs automatically.
moduleNoOptional module name to group this file with related code (e.g., "blog-posts", "user-auth"). Module is auto-created if it doesn't exist.
attributesNoPHP 8 class-level attributes (e.g., ["Fillable(['name', 'email'])"], ["ObservedBy(UserObserver::class)"]). Use search_attributes tool to find available attributes.
Behavior4/5

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

No annotations provided, so description carries full burden. Discloses that it creates an empty shell, returns UUID, auto-creates app.js for Vue, and details conditional actions based on appJs response. Could mention side effects like auto-creation, but overall good for no annotations.

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?

Well-structured with clear paragraphs and a bold IMPORTANT section. Front-loaded with main purpose. Though lengthy, each part adds value; could be slightly more concise but remains clear and informative.

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?

Given 8 parameters, 3 required, no output schema, and complex Vue behavior, the description is comprehensive. It explains Vue appJs response handling and references other tools (save_file, search_attributes). No gaps left for an AI agent to misuse.

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%, baseline 3. Description adds context: explains type for PHP vs Vue, auto-resolving includes, namespace usage, and appJs handling. Adds meaningful usage examples beyond schema definitions.

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 creates an 'empty file shell' in a Stellify project and returns a file UUID. It distinguishes from sibling tools like create_directory and create_element by specifying it's for files and providing details for PHP and Vue.

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?

Provides clear guidance on file types (PHP: class/model/controller/middleware; Vue: type='js', extension='vue') and explains auto-creation of app.js and template route. Includes an IMPORTANT section for checking appJs response. Missing explicit when-not-to-use or mention of alternatives but still strong.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Stellify-Software-Ltd/stellify-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server