Skip to main content
Glama
codyde
by codyde

createfile

Generate and save files by specifying a file path and content, enabling automated file creation through the MCP File Server interface.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
contentYesContent to write to the file
filePathYesPath where the file should be created

Implementation Reference

  • The handler function for the createfile tool, which ensures the directory exists, writes the file content using fs.writeFile, updates Sentry span with metrics, and returns success or error message.
        async ({ filePath, content }) => {
            return await Sentry.startSpan(
                {
                    name: "createFile",
                    op: "tool.createfile",
                    attributes: {
                        'file.path': filePath,
                        'file.content.length': content.length
                    }
                },
                async (span) => {
                    try {
                        // Ensure the directory exists
                        const dirPath = path.dirname(filePath);
                        span.setAttribute('file.directory', dirPath);
    
                        try {
                            await fs.mkdir(dirPath, { recursive: true });
                            span.setAttribute('directory.created', true);
                        } catch (mkdirError) {
                            // Directory might already exist, just log this to the span
                            span.setAttribute('directory.creation.error', mkdirError.message);
                        }
    
                        // Write the file
                        const startTime = Date.now();
                        await fs.writeFile(filePath, content, 'utf8');
                        const endTime = Date.now();
    
                        // Update span with file details
                        const fileStats = await fs.stat(filePath);
    
                        span.setAttributes({
                            'file.size': fileStats.size,
                            'operation.duration_ms': endTime - startTime
                        });
                        span.setStatus("ok");
    
                        return {
                            content: [
                                {
                                    type: "text",
                                    text: `File created successfully at: ${filePath}\nSize: ${fileStats.size} bytes`
                                }
                            ]
                        };
                    } catch (error) {
                        // Add error information to the span
                        span.setAttributes({
                            'error.message': error.message,
                            'error.stack': error.stack
                        });
                        span.setStatus("error");
    
                        // Capture the exception for Sentry
                        Sentry.captureException(error);
    
                        return {
                            content: [
                                {
                                    type: "text",
                                    text: `Error creating file: ${error.message}`
                                }
                            ]
                        };
                    }
                }
            );
        }
    )
  • Zod input schema defining filePath and content parameters for the createfile tool.
    {
        filePath: z.string().describe("Path where the file should be created"),
        content: z.string().describe("Content to write to the file")
    },
  • src/index.js:24-100 (registration)
    Registration of the createfile tool using server.tool() with name, input schema, and handler function.
    server.tool(
        "createfile",
        {
            filePath: z.string().describe("Path where the file should be created"),
            content: z.string().describe("Content to write to the file")
        },
        async ({ filePath, content }) => {
            return await Sentry.startSpan(
                {
                    name: "createFile",
                    op: "tool.createfile",
                    attributes: {
                        'file.path': filePath,
                        'file.content.length': content.length
                    }
                },
                async (span) => {
                    try {
                        // Ensure the directory exists
                        const dirPath = path.dirname(filePath);
                        span.setAttribute('file.directory', dirPath);
    
                        try {
                            await fs.mkdir(dirPath, { recursive: true });
                            span.setAttribute('directory.created', true);
                        } catch (mkdirError) {
                            // Directory might already exist, just log this to the span
                            span.setAttribute('directory.creation.error', mkdirError.message);
                        }
    
                        // Write the file
                        const startTime = Date.now();
                        await fs.writeFile(filePath, content, 'utf8');
                        const endTime = Date.now();
    
                        // Update span with file details
                        const fileStats = await fs.stat(filePath);
    
                        span.setAttributes({
                            'file.size': fileStats.size,
                            'operation.duration_ms': endTime - startTime
                        });
                        span.setStatus("ok");
    
                        return {
                            content: [
                                {
                                    type: "text",
                                    text: `File created successfully at: ${filePath}\nSize: ${fileStats.size} bytes`
                                }
                            ]
                        };
                    } catch (error) {
                        // Add error information to the span
                        span.setAttributes({
                            'error.message': error.message,
                            'error.stack': error.stack
                        });
                        span.setStatus("error");
    
                        // Capture the exception for Sentry
                        Sentry.captureException(error);
    
                        return {
                            content: [
                                {
                                    type: "text",
                                    text: `Error creating file: ${error.message}`
                                }
                            ]
                        };
                    }
                }
            );
        }
    )
Behavior1/5

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

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

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

Completeness1/5

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

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

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

Related 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/codyde/mcp-file-tool'

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