Skip to main content
Glama

quilt_write

Create or overwrite a file while recording the writing agent as the author for exact attribution, and deny writes if another agent holds the path to prevent conflicts.

Instructions

Create or overwrite a whole file through Quilt instead of your raw editor, recording YOU as the author of its contents at write time, so attribution is exact even when several agents share this checkout, with no claims or reconcile guesswork. Use this for new files; use quilt_edit to change part of an existing one. Pass why (your ticket/task). If another agent holds this path, the write is denied with their intent so you can reconcile instead of clobbering.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
whyNoa short why for this write, e.g. the ticket/task
pathYesfile path (repo-relative or absolute; stored repo-relative)
actorNoactor id to act as. Auto-derived per connection when omitted (from the client name, e.g. cursor-3fa2), so naming is optional for a single agent. Pass an explicit id (your role/task name) when several subagents share one server — they have no ambient identity to tell them apart — or when you want a stable id across runs.
contentYesfull file contents to write
Behavior4/5

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

No annotations provided, so description carries full burden. It clearly explains authorship recording, attribution exactness, and the denial behavior when another agent holds the path. However, it lacks details on atomicity or error handling.

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 a single paragraph of four sentences, each adding essential information. It front-loads the main purpose, then provides usage guidelines and behavioral notes. No redundant or superfluous text.

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 tool without output schema, the description adequately covers how to use, when to use, and what behavioral guarantees exist. It does not describe return values or error messages, but given the simplicity, it is mostly complete.

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 description coverage is 100%, but the description adds value by explaining the 'why' parameter's purpose ('your ticket/task') and the 'actor' parameter's auto-derivation logic and when to use an explicit ID. The 'path' and 'content' are sufficiently described.

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 uses specific verbs ('Create or overwrite') and clearly identifies the resource ('a whole file through Quilt'). It distinguishes from sibling tool 'quilt_edit' by stating the scope ('new files' vs 'change part of an existing one').

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?

Explicitly states when to use this tool ('Use this for new files') and when to use the sibling ('use quilt_edit to change part of an existing one'). Also provides guidance on passing 'why' and warns about concurrent access denial.

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/wkoverfield/quilt'

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