Skip to main content
Glama
peeyushcodes

Windows Developer MCP Server

write_file

Create or overwrite a file with specified text content, automatically creating parent directories. Supports custom encoding and optional confirmation for secure environments.

Instructions

    Create or overwrite a file with the given content.

    Creates parent directories automatically. Overwrites existing files
    without warning — use file_exists() first if unsure.

    Requires explicit confirmation when ``security.require_confirmation``
    is enabled in config.

    Args:
        path:     Path to write (absolute or relative to cwd).
        content:  The text content to write.
        encoding: File encoding. Default: "utf-8".
        confirm:  Set to True to confirm when required by config.

    Returns:
        A dict with keys: status, data (path, size_bytes, lines).

    Examples:
        write_file("notes.txt", "Hello, World!")
        write_file("src/config.py", "DEBUG = True

", confirm=True)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYes
confirmNo
contentYes
encodingNoutf-8

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

With no annotations, the description carries full burden. It discloses automatic parent directory creation, destructive overwrite behavior, and confirmation requirements, covering all key side effects.

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 well-organized with sections for behavior, args, returns, and examples. Every sentence adds value and the examples clarify usage.

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

Completeness5/5

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

Given the tool has 4 parameters and an output schema, the description explains the return dict structure, parameter defaults, and edge cases, making it complete without needing to inspect the schema.

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

Parameters5/5

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

The schema has 0% coverage (no per-parameter descriptions), but the description's Args section explains each parameter's meaning and defaults, fully compensating for the schema gap.

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?

The description starts with 'Create or overwrite a file with the given content,' which clearly identifies the action and resource. It distinguishes from siblings like append_file and read_file by explicitly stating overwrite behavior.

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

Usage Guidelines5/5

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

Provides explicit guidance: 'Overwrites existing files without warning — use file_exists() first if unsure' and mentions config-dependent confirmation. This tells the agent when to be cautious and when to use an alternative check.

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/peeyushcodes/windows-developer-mcp'

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