Skip to main content
Glama

find_and_replace_buf

Find and replace exact text in a Neovim buffer with undoable in-memory edit. Requires single occurrence; include surrounding lines to disambiguate. Creates buffer if missing.

Instructions

Find and replace text in a Neovim buffer. The edit happens in-memory and is fully undoable — nothing is written to disk until the user saves.

file: path relative to Neovim's cwd (as shown in get_state buffers). old_string: the exact text to find. Must match exactly once in the buffer; returns an error if not found or if it matches multiple locations. Include surrounding lines to disambiguate. new_string: the replacement text.

Creates the buffer if it doesn't already exist. Use this for targeted edits. Use write_full_buf instead when replacing the entire buffer content. Use read_full_buf or read_buf_range first if you need to see the current content before editing.

Returns {start_line, lines_removed, lines_added, total_lines} on success, or {error} with a message on failure.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fileYes
old_stringYes
new_stringYes
Behavior4/5

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

Describes in-memory edit, undoability, and that nothing is written to disk until save. Also mentions buffer creation and return format. However, lacks explicit statement that it is a mutation tool, though implied.

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?

Well-structured with purpose, parameters, usage, and return. Slightly verbose but every sentence adds value. Efficient overall.

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?

Covers uniqueness constraint, buffer creation, return format, and alternatives. Minor ambiguity about invalid file paths, but otherwise complete for the complexity level.

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?

Adds detailed meaning beyond the bare schema: explains file path relative to cwd, old_string must match exactly once, suggests disambiguation. Schema has 0% coverage, so description compensates fully.

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 tool finds and replaces text in a Neovim buffer, specifying the resource and action. It distinguishes from sibling tools like write_full_buf and read_buf_range.

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 (targeted edits) and provides alternatives (write_full_buf, read_buf_range). Also describes error conditions for old_string 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/paulburgess1357/nvim-mcp'

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