Skip to main content
Glama
BasilSkyWalk

parecode

by BasilSkyWalk
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Local

ParecodeEdit

Apply many edits across many files in one call with atomic per-file safety and conflict detection. Use line-range ops with anchor verification or fuzzy string patches.

Instructions

Apply many edits across many files in one call — the edit counterpart to ParecodeSearch/ParecodeExpand. Prefer over native Edit/MultiEdit for 2+ edits to one file, edits across files (files apply in parallel), or one logical revision that should land together. Each item is a line-range op (replaceLines or insertAfter, guarded by an expect anchor) or a string-patch op (oldString/newString; fuzzy:true tolerates whitespace drift, 'aggressive' also normalizes Unicode look-alikes). Strongly prefer line-range ops when you know the target lines — e.g. the line numbers ParecodeSearch returned: a line number plus a short expect anchor skips constructing exact-match snippets, so recurring text (a repeated call) can't trigger the multiple-match errors and retries an oldString needs extra context to avoid. Reserve oldString for edits with no known lines. Atomicity is per file, NOT cross-file: within a file all ops apply or none, other files commit independently — check each result's status. Writes are atomic with mtime conflict detection; fuzzy fails closed on low confidence or ambiguity.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
editsYesList of edit operations to perform

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed3 schema fields changedv0.9.1
    • changedInput schema / properties / edits / items / properties / expect / description
      Previous value: -"Anchor verifying the target before any write: the trimmed first line, or first and last line joined by `\\n…\\n` for ranges. If the lines drifted it is re-located by fuzzy match within ±20 lines at ≥0.85 confidence; if not found, the op returns snippet_mismatch and nothing in that file is written."New value: +"Anchor verifying the target before any write: the trimmed first line, or first and last line joined by `\\n…\\n` for ranges. If the lines drifted, the first-line anchor is re-located within ±20 lines, the range keeps its original length, and the last-line anchor is re-verified at the new position. Relocating a multi-line replaceLines range requires the two-ended (`\\n…\\n`) form — a single-line anchor that has drifted returns snippet_mismatch rather than overwriting an unverified range. If the anchor is missing or matches more than one nearby location, the op returns snippet_mismatch and nothing in that file is written."
    • changedInput schema / properties / edits / items / properties / file / description
      Previous value: -"Path (absolute or relative) to the file to edit. Edits are grouped by file and applied all-or-nothing per file; the per-file status is one of success, conflict (file changed underneath the edit), error, snippet_mismatch, or fuzzy_match_failed."New value: +"Path (absolute or relative) to the file to edit. Edits are grouped by file and applied all-or-nothing per file; the per-file status is one of success, conflict (file changed underneath the edit), error, snippet_mismatch, or fuzzy_match_failed. On snippet_mismatch the op result carries an `actual` snapshot (line-numbered current contents at the target) so you can correct the anchor/line numbers in place without re-reading the file."
    • changedInput schema / properties / edits / items / properties / fuzzy / description
      Previous value: -"String-patch tolerance: true = whitespace-insensitive matching; 'aggressive' = also normalize Unicode look-alikes (NFKD). Below 0.85 confidence it fails closed (fuzzy_match_failed) rather than guessing. Omit for exact-only matching."New value: +"String-patch tolerance: true = whitespace-insensitive matching; 'aggressive' = also normalize Unicode look-alikes (NFKD). Beyond whitespace it tolerates only ~5% character drift — short strings must match exactly after whitespace normalization — and it fails closed (fuzzy_match_failed) rather than guessing; if several locations match, the op errors out instead of picking one. Replacements adopt the file's existing indentation when it differs from oldString. Omit for exact-only matching."
  2. First observedv0.5.1

TDQS

A4.9/5.0
Behavior5/5

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

With no annotations, the description fully discloses behavioral traits: per-file atomicity, conflict detection, error statuses (snippet_mismatch, fuzzy_match_failed), anchor relocation, fuzzy matching tolerance, and indentation adoption. It covers safety and failure modes comprehensively.

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 dense and front-loaded with the core purpose, but it is long. Every sentence adds value, though some could be more succinct. Overall well-structured but slightly verbose for the amount of information.

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's complexity, no annotations, and no output schema, the description is remarkably complete. It covers purpose, usage guidelines, detailed parameter semantics, behavioral traits, and error handling. No gaps identified.

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?

Despite 100% schema coverage, the description adds substantial meaning beyond the schema by explaining the trade-offs between line-range and string-patch ops, the details of expect anchor behavior, fuzzy matching nuances, and per-file atomicity. It provides context that the schema alone does not.

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 it applies many edits across many files, identifies itself as the edit counterpart to ParecodeSearch/ParecodeExpand, and lists specific use cases (2+ edits to one file, edits across files, one logical revision). This distinguishes it from siblings and provides a clear purpose.

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 gives when to prefer this tool over alternatives (native Edit/MultiEdit) and provides detailed guidance on choosing between line-range ops and string-patch ops, including when to use each and the behavior of expect anchors and fuzzy matching.

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