Skip to main content
Glama

Write File

write_file
Destructive

Write text to a file, creating parent directories automatically. Overwrites by default or appends when specified.

Instructions

Write text to a file, creating parent directories as needed. Overwrites by default; set append=true to append.

Args:

  • path (string): Destination file path.

  • content (string): Text to write.

  • append (boolean): Append instead of overwrite (default false).

Returns a confirmation with bytes written.

Example: { "path": "~/notes.txt", "content": "hello", "append": true }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesDestination path
contentYesText content to write
appendNoAppend instead of overwrite
Behavior5/5

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

Annotations already indicate destructive, non-read-only, and non-idempotent nature. The description adds valuable behavioral details: directory creation, overwrite default, append option, and confirmation return. No contradictions.

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-structured: summary sentence, Args list, Returns, and Example. Every sentence adds value with no fluff. Concise and front-loaded with key behavior.

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?

For a simple 3-parameter tool without output schema, the description covers behavior, all parameters, return value, and an example. Complete for its complexity.

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

Parameters4/5

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

Schema coverage is 100% with good descriptions. The tool description reiterates parameters but adds an example and return type (bytes written), providing extra context 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?

The description clearly states the action ('Write text to a file'), the resource ('file'), and adds specific context ('creating parent directories as needed'). This distinguishes it from siblings like read_file or edit_file.

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?

The description explains when to use different modes (overwrite vs append), but does not explicitly compare with sibling tools or state when not to use this tool. It's clear within the tool's domain but lacks cross-tool guidance.

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/highercomve/mcptools'

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