Coding Agent MCP Server

Overview Schema Source Related Servers Discussions Admin

create_file

Create a new file at a specified path, with optional initial content, ability to overwrite existing files, and automatic creation of parent directories.

Instructions

Create a new file with optional content

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": {
      "path": "<path>"
    },
    "name": "create_file"
  }
}

Input Schema

Name	Required	Description
`path`	Yes	Path to the new file
`content`	No	Initial content for the file
`overwrite`	No	Overwrite if file exists
`createDirs`	No	Create parent directories if they don't exist

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.1May 29, 2026

TDQS

B3.2/5.0

Behavior2/5

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

No annotations provided, so description bears full burden. It fails to mention key behaviors: what happens on overwrite when false, error conditions, or that parent directories are created by default. The only behavioral hint is 'new file', which implies no modification of existing content but doesn't cover overwrite scenario.

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?

Single sentence, no wasted words, front-loaded with action and object. Highly efficient.

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 complexity of file operations and many sibling tools (e.g., write_file, edit_file), the description is too brief. It omits when to use this vs others, does not explain overwrite behavior beyond schema, and lacks notes on error handling or idempotency. Incomplete for a 4-parameter tool with no output schema.

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% with clear parameter descriptions. The description adds no extra meaning beyond restating 'optional content' which is already in the schema. Baseline score of 3 applies as schema does the heavy lifting.

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?

Description uses clear verb 'Create' and resource 'file' with modifier 'new' and 'optional content'. Distinguishes from siblings like 'write_file' which likely modifies existing files, and 'copy_file'/'move_file' which operate on existing files.

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?

No guidance on when to use this tool versus alternatives like 'write_file' (which may overwrite unconditionally) or 'edit_file'. No context on prerequisites or when not to use it. The description lacks usage direction.

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