Skip to main content
Glama

ParecodeEdit

Apply multiple edits across files in a single call, with atomic per-file commits, conflict detection, and fuzzy matching for drifted code.

Instructions

Apply many edits across many files in one call — the edit counterpart to ParecodeSearch/ParecodeExpand. Prefer over native Edit/MultiEdit when: (a) making 2+ edits to one file, or edits across files (files apply in parallel); (b) an oldString from an earlier read may have drifted — set fuzzy:true (whitespace-tolerant) or fuzzy:'aggressive' (also normalizes Unicode look-alikes); (c) the changes are one logical revision that should land together. Each item is either a line-range op (replaceLines or insertAfter, each guarded by an expect anchor — the primary path) or a string-patch op (oldString/newString — the fallback). Atomicity is per file, NOT cross-file: within a file all ops apply or none do, but other files commit independently, so check each result's status. Writes are atomic (temp+rename) with mtime conflict detection (a concurrent external edit returns conflict with no write); fuzzy matching fails closed below 0.85 confidence.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
editsYesList of edit operations to perform
Behavior5/5

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

With no annotations, the description fully discloses atomicity (per file, not cross-file), mtime conflict detection, fuzzy matching thresholds (0.85 confidence, fail-closed), and possible statuses (success, conflict, error, etc.). This is comprehensive for safe invocation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single dense paragraph but well-organized, front-loading purpose and usage then delving into details. It could benefit from bullet points for clarity, but it is not verbose or wasteful.

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?

Given the complexity (two op types, atomicity, conflict detection) and lack of output schema, the description covers return statuses and behavioral nuances adequately. It is complete enough for an agent to use correctly.

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%, and the description adds significant context beyond the schema, such as how the 'expect' anchor works for line-range ops, the behavior of 'fuzzy' matching, and the fallback nature of string-patch ops. This enhances understanding.

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 that ParecodeEdit is the counterpart to ParecodeSearch/ParecodeExpand, designed for applying many edits across files. It explicitly distinguishes from siblings by naming them and provides specific use cases.

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 gives explicit conditions (a, b, c) for preferring this tool over native Edit/MultiEdit, and outlines two op modes (line-range vs string-patch). It does not explicitly state when not to use it, but the guidance is clear and actionable.

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/BasilSkyWalk/parecode'

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