Skip to main content
Glama
Claude Free Code MCP

Claude Free Code MCP

by ImIpscanning

write_file

Destructive

Create UTF-8 files or replace existing ones with explicit overwrite permission, while capturing snapshots for change tracking.

Instructions

Create a UTF-8 file. Overwriting an existing file requires overwrite=true. Changes get snapshots.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "file": "<file>",
      "content": "<content>"
    },
    "name": "write_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileYesRelative file path
contentYesUTF-8 file content
overwriteNoPermit replacement of existing file
expectedSha256NoOptional expected SHA-256 (empty if not existing)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already flag this as destructive and non-read-only, and the description adds meaningful context beyond them: the overwrite gate and the fact that changes are snapshotted (implying recoverability). It stops short of explaining what happens on a SHA-256 mismatch or whether parent directories are created.

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 terse sentences with the core action first and the destructive precondition immediately after. Nothing is wasted or redundant.

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 four-parameter mutation tool with no output schema, the definition covers the operation, the overwrite safety gate, and snapshot behavior, which is enough to call it correctly. Marginal gaps remain around path creation and concurrency/expectedSha256 failure semantics.

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 all four parameters are documented structurally; the description reinforces the overwrite requirement but adds no new detail. The expectedSha256 parameter, whose schema text is cryptic ("empty if not existing"), gets no clarification in the description.

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 states a specific verb and resource ("Create a UTF-8 file") and adds an encoding constraint, so the operation is unambiguous. It does not distinguish itself from write-adjacent siblings such as edit_lines or project_notes_write, leaving that differentiation to the agent.

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

Usage Guidelines3/5

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

One real usage condition is given: replacing an existing file requires overwrite=true. There is no guidance on when to choose this tool over edit_lines or other write paths, and no exclusions, so usage is implied rather than fully framed.

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