Skip to main content
Glama

Set vimrc

set_vimrc
Destructive

Write a vimrc, replacing the whole text; an empty text clears it. Your own, or with 'projectKey' that project's (its owner or a board administrator only). Up to 8000 characters. Lines the editor does not read are saved anyway and returned in 'warnings'. For your own, 'ignoreProjectVimrc' switches projects' vimrcs off or on for you; give 'vimrc', 'ignoreProjectVimrc' or both. Read: 'set' with number (nu), hlsearch (hls), incsearch (is), ignorecase (ic), smartcase (scs), wrapscan (ws) and clipboard=unnamed|unnamedplus in vim's spellings (no…, inv…, !, &); 'syntax on|off'; 'let mapleader = ","'; and map, nmap, vmap, xmap, imap, noremap, nnoremap, vnoremap, xnoremap, inoremap of plain keys and . Comments (") and blank lines are fine. Any other line is not an error: it is kept, skipped by the editor and named in 'warnings' with its line.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "set_vimrc"
  }
}

Input Schema

NameRequiredDescriptionDefault
vimrcNoThe whole vimrc. Left out (for your own): the text is kept and only the switch changes.
projectKeyNoA project key, e.g. 'PM', to write that project's vimrc. Left out: your own.
ignoreProjectVimrcNoYour own only: true — projects' vimrcs do not apply to you.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

The annotations already flag destructive=true, but the description adds substantial context: whole-text replacement, clearing via empty text, the 8000-character limit, owner/admin authorization, and that unread lines are retained and reported in 'warnings'. That goes well beyond the structured annotations.

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

Conciseness3/5

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

The core operation is front-loaded and readable, but the description is long and dense, especially the full enumeration of accepted vim settings. The warning behavior is stated twice—once as 'saved anyway and returned in warnings' and again in the final sentence—so some compression is possible.

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?

For a destructive, no-output-schema, three-parameter tool, the description covers permissions, size limits, replacement semantics, accepted syntax, warning behavior, and parameter combinations. It is complete enough for an agent to invoke it safely.

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 schema already documents defaults and left-out behavior. The description still adds meaningful constraints: empty text clears the config, project writes require owner/admin rights, and for the user's own config one must pass 'vimrc', 'ignoreProjectVimrc', or both; the syntax details are not parameter-specific.

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 first clause specifies the verb and resource ('Write a vimrc'), clarifies whole-text replacement, empty-text clearing, and scopes it to the user's own or a project's config. This clearly separates it from the read-only sibling get_vimrc.

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?

It explains the own-vs-project choice, the owner/board-administrator permission gate, and that for the user's own config one must supply 'vimrc', 'ignoreProjectVimrc', or both. It does not explicitly say to use get_vimrc for reading, so guidance is strong but not fully complete.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources