Skip to main content
Glama
Stellify-Software-Ltd

Stellify MCP Server

Official

save_file

Finalize and save a file by replacing its full content. Provide the file UUID, name, and type; include context fields for significant changes.

Instructions

Finalize a file. Full replacement - call get_file first to update existing files.

Required: uuid, name, type. For significant changes, include context fields: summary, rationale, references, decisions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
uuidYesUUID of the file to save
nameYesFile name (without extension)
typeYesFile type: "js" for JavaScript/Vue, others for PHP
extensionNoFile extension: "vue" for Vue SFCs, "js" for JavaScript
templateNoRoot element UUIDs for Vue <template>
dataNoMethod UUIDs (from create_method)
statementsNoStatement UUIDs (imports, variables, refs)
includesNoFile UUIDs for local imports (e.g., Vue components imported by app.js) AND framework class UUIDs/namespaces. CRITICAL: For JS mount files, add imported Vue component UUIDs here or they won't be bundled. Use models array for project models.
modelsNoProject model UUIDs (auto-namespaced). Do NOT duplicate in includes.
frameworkImportsNoStellify framework modules to import (e.g., ["Http", "Form", "Collection"]). Auto-generates: import { Http, Form, Collection } from 'stellify-framework';
summaryNoContext: What this file does and why it exists
rationaleNoContext: Why it was built this way
referencesNoContext: Related entities [{uuid, type, relationship, note}]
decisionsNoContext: Design decisions
attributesNoPHP 8 class-level attributes (e.g., ["Fillable(['name', 'email'])"], ["ObservedBy(UserObserver::class)"]). Use search_attributes tool to find available attributes.
Behavior2/5

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

No annotations provided, so description must disclose behavior. It states 'Full replacement' but does not detail side effects, destructive impact, permissions, or error states. The description is minimal on behavioral traits.

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 concise sentences, front-loaded with purpose and requirement. No unnecessary words, efficient communication.

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

Completeness2/5

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

Given 15 parameters and no output schema, the description provides only a high-level summary. It does not explain parameter interplay (e.g., includes vs models) or workflow beyond 'call get_file first'. Incomplete for complex usage.

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 coverage is 100%, so baseline is 3. Description reiterates required fields and context fields but adds little new meaning beyond the schema's detailed parameter 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?

Clearly states 'Finalize a file. Full replacement', indicating the specific action and semantics. Distinguishes from create_file by noting to call get_file first for updates.

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?

Explicitly advises to call get_file first for updating existing files, and lists required fields. However, does not explicitly contrast with alternatives like create_file or provide negative use cases.

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