Skip to main content
Glama

write_full_buf

Replace the entire content of a Neovim buffer with new text. Edits are in-memory and undoable; nothing is written to disk until you save.

Instructions

Replace the entire content of 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). content: the full new text for the buffer.

Creates the buffer if it doesn't already exist. Use this when you need to rewrite the whole file. Use find_and_replace_buf instead for targeted edits that preserve surrounding content.

Returns {total_lines} with the new line count.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fileYes
contentYes
Behavior5/5

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

Discloses in-memory edit, undoability, no disk write until user saves, buffer creation, and return value. No annotations provided, but description fully covers behavioral traits.

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?

Concise and well-structured, with main purpose front-loaded and no unnecessary words. Every sentence adds value.

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?

Complete for a two-parameter tool with no output schema: covers output, creation behavior, undo, and disk write, plus usage alternatives.

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 meaning beyond schema: explains file path relative to Neovim cwd and content as full new text, compensating for 0% schema description coverage.

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 'Replace the entire content of a Neovim buffer' with a specific verb and resource, and distinguishes from sibling tool find_and_replace_buf by specifying when to use each.

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?

Explicit guidelines: 'Use this when you need to rewrite the whole file' and 'Use find_and_replace_buf instead for targeted edits', plus mentions buffer creation behavior.

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