Skip to main content
Glama

get_state

Retrieve a complete snapshot of the Neovim session, including all windows, buffers, mode, folds, marks, diagnostics, highlights, and indent settings.

Instructions

Full snapshot of the current Neovim session. Read-only — does not modify any editor state.

Use get_state_brief for quick orientation at the start of a turn. Use this when you need the complete picture: all window details, folds, marks, diagnostics summaries, highlights, virtual text, and indent settings.

Returns: mode (normal/insert/visual/etc.), cwd, buffers (relative paths of all listed buffers), modified_buffers, current_tab, tab_count.

windows — list of visible windows (current tab only). The active window is always first, the alternate window (previous) is second. Each window entry contains: file (path relative to cwd), filetype, total_lines, modified, buftype ("file" for normal buffers, "terminal", etc.), line, col, indent: {expandtab, shiftwidth, tabstop}. Optional per-window fields (present when applicable):

  • role: "active" or "alternate".

  • context: numbered lines surrounding the cursor.

  • selection: {start_line, start_col, end_line, end_col} in visual modes.

  • folds: list of [start, end] closed fold ranges.

  • diagnostics_summary: {error, warning, info, hint} counts.

  • marks: list of {mark, line, col} for lowercase (a-z) buffer marks.

  • mcp_highlights: list of {start_line, end_line, color} for active highlights.

  • mcp_virtual_text: list of {line, position, lines, color} for active virtual text.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

Explicitly states 'Read-only — does not modify any editor state.' No annotations exist, so the description fully covers behavioral transparency.

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 for the amount of information. Could be marginally more concise while retaining detail.

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?

Fully complete given no complex parameters or output schema. Every aspect of the tool's behavior and return structure is explained in detail.

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?

No parameters to describe (0 parameters, 100% schema coverage). The description adds value by explaining the extensive return structure beyond what schema provides.

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 returns a 'full snapshot of the current Neovim session' and lists all components. It explicitly distinguishes from the sibling 'get_state_brief' by noting 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?

Directly provides usage guidance: 'Use get_state_brief for quick orientation at the start of a turn. Use this when you need the complete picture.'

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