Skip to main content
Glama
j0hanz

filesystem-mcp

by j0hanz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Create Files

create
Destructive

Write whole text files by overwriting or appending content, and generate missing parent directories automatically.

Instructions

Write whole text files: create new ones, overwrite, or append. Missing parent directories are created. edit or patch changes part of an existing file.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filesYesList of files to create (max 100); each entry requires path and content; combined content is capped at the file-size limit

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.7.0
    • changedInput schema / properties / files / description
      Previous value: -"List of files to create (max 100); each entry requires path and content"New value: +"List of files to create (max 100); each entry requires path and content; combined content is capped at the file-size limit"
  2. Changed1 schema field changedv2.4.1
    • addedInput schema / $schema
      Added value: +"https://json-schema.org/draft/2020-12/schema"
  3. Changed2 schema fields changedv2.3.0
    • addedInput schema / properties / files / items / properties / append
      Added value: +{
+  "description": "Append the content to the end of the file instead of overwriting; creates the file if it does not exist",
+  "type": "boolean"
+}
    • addedInput schema / properties / files / items / properties / overwrite
      Added value: +{
+  "description": "Replace an existing file without asking the user; without it an existing file prompts for confirmation",
+  "type": "boolean"
+}
  4. Addedv2.0.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations declare destructiveHint=true and readOnlyHint=false; the description adds real value beyond them by disclosing that missing parent directories are created and by flagging the whole-file overwrite/append semantics. It does not cover the return value or the confirmation prompt behavior (that lives in the schema), keeping it below 5.

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?

Two sentences, zero filler, with the core verb-and-resource statement front-loaded and the sibling disambiguation immediately after. Every clause earns its place.

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 write tool with no output schema, the description covers modes, side effects, and sibling routing adequately. It omits batching behavior and what the call returns (paths, confirmation results), which are minor but real gaps.

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% and the schema already documents path, content, append, and overwrite thoroughly, so the baseline is 3. The description echoes the create/overwrite/append modes but adds no syntax or format detail beyond the schema.

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?

States a specific verb and resource ('Write whole text files') and enumerates the modes (create, overwrite, append). It explicitly distinguishes itself from the edit and patch siblings, so an agent can route without opening schemas.

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 names the alternatives (edit, patch) and the boundary condition that selects them: those change part of an existing file, whereas this writes whole files. There is no explicit when-not guidance (e.g. for binary files or very large files), so it falls just short of 5.

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