Skip to main content
Glama
ai-yliu

Filesystem MCP Server

by ai-yliu

write_file

Create or update files by writing content to specified paths in the filesystem.

Instructions

Create new file or overwrite existing

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesPath to the file to write
contentYesContent to write to the file

Implementation Reference

  • Handler for the 'write_file' tool. Extracts path and content from arguments, validates the path, ensures the parent directory exists, writes the file using fs.writeFile, and returns a success message.
    case 'write_file': {
      const { path: filePath, content } = request.params.arguments as { 
        path: string; 
        content: string 
      };
      validatePath(filePath);
      
      // Ensure parent directory exists
      await fs.ensureDir(path.dirname(filePath));
      await fs.writeFile(filePath, content, 'utf8');
      
      return {
        content: [
          {
            type: 'text',
            text: `File written successfully: ${filePath}`,
          },
        ],
      };
    }
  • src/index.ts:127-143 (registration)
    Registers the 'write_file' tool in the ListTools response, including name, description, and input schema definition.
      name: 'write_file',
      description: 'Create new file or overwrite existing',
      inputSchema: {
        type: 'object',
        properties: {
          path: {
            type: 'string',
            description: 'Path to the file to write',
          },
          content: {
            type: 'string',
            description: 'Content to write to the file',
          },
        },
        required: ['path', 'content'],
      },
    },
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It mentions 'overwrite existing' which implies destructive behavior, but doesn't disclose critical traits like permissions required, whether it creates parent directories, error handling (e.g., if path is invalid), or rate limits. This is a significant gap for a mutation tool.

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?

The description is a single, efficient sentence with zero waste. It's front-loaded with the core action and appropriately sized for a simple tool, making it easy to parse quickly.

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 the tool's complexity (a mutation operation with no annotations and no output schema), the description is incomplete. It lacks behavioral details (e.g., side effects, error cases) and doesn't explain return values or success criteria, which is inadequate for a write operation.

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 100%, so the schema already documents both parameters ('path' and 'content') adequately. The description doesn't add any meaning beyond what the schema provides (e.g., no details on path format or content encoding). Baseline 3 is appropriate when the schema does the heavy lifting.

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?

The description clearly states the action ('Create new file or overwrite existing') which is a specific verb+resource combination. It distinguishes from siblings like 'read_file' or 'move_file' by focusing on writing content. However, it doesn't explicitly differentiate from all siblings (e.g., 'create_directory' is also a creation tool).

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., path must exist), when not to use it (e.g., for appending vs overwriting), or explicit alternatives among siblings like 'move_file' for relocation or 'read_file' for reading.

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/ai-yliu/filesystem-mcp-server'

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