Skip to main content
Glama

find_and_replace_buf

Find exact text in a Neovim buffer and replace it in-memory, with undoable changes. Requires a unique match; returns error if not found or multiple. Use for targeted edits after reading the buffer content.

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
Behavior5/5

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

Discloses key behaviors: in-memory edit (undoable, not written to disk until save), and that it creates the buffer if it doesn't exist. No annotations present, so description carries full burden.

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 clear sections, but slightly verbose. Front-loaded with purpose and behavior. Every sentence adds value, but could be tightened.

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?

Covers parameter constraints, error conditions, return value details, and behavioral nuances. Despite no output schema, the description provides return format and failure indication, making it complete for an agent.

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?

Adds meaning beyond schema: explains file path relative to cwd, conditions for old_string (exact single match, disambiguation), and new_string role. Schema coverage is 0%, so description compensates well.

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's action: 'Find and replace text in a Neovim buffer.' It specifies verb+resource and differentiates from sibling tools like write_full_buf, read_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?

Provides explicit when-to-use guidance: targeted edits; alternatives like write_full_buf for full replacement and read tools for preview. Also specifies constraint that old_string must match exactly once.

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