Skip to main content
Glama
marekrost

mcp-server-spreadsheet

insert_columns

Add blank columns to spreadsheets by specifying position and quantity, shifting existing columns right to organize data.

Instructions

Insert one or more blank columns, shifting existing columns right.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fileYesPath to the spreadsheet file
columnYes1-based column index where new columns will be inserted (e.g. 1 = A, 2 = B). Existing columns at and to the right shift right.
countNoNumber of blank columns to insert
sheetNoSheet name. Defaults to the first sheet if omitted.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The 'insert_columns' tool handler implemented in src/mcp_server_spreadsheet/server.py.
    def insert_columns(
        file: Annotated[str, Field(description="Path to the spreadsheet file")],
        column: Annotated[int, Field(description="1-based column index where new columns will be inserted (e.g. 1 = A, 2 = B). Existing columns at and to the right shift right.")],
        count: Annotated[int, Field(description="Number of blank columns to insert")] = 1,
        sheet: Annotated[str | None, Field(description="Sheet name. Defaults to the first sheet if omitted.")] = None,
    ) -> str:
        """Insert one or more blank columns, shifting existing columns right."""
        wb = load_workbook(file)
        ws = _resolve_sheet(wb, sheet)
        ws.insert_cols(column, count)
        wb.save(file)
        return f"Inserted {count} columns at column {column}"
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions the insertion action and column shifting, but omits critical details like whether this is a destructive mutation (implied by 'shifting'), error conditions (e.g., invalid column index), or side effects (e.g., formula references might break).

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?

The description is a single, efficient sentence that front-loads the core action ('insert one or more blank columns') and adds essential context ('shifting existing columns right'). There is zero wasted verbiage.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's moderate complexity (mutation with 4 parameters), no annotations, but a rich input schema (100% coverage) and output schema (present), the description is minimally adequate. It covers the basic operation but lacks behavioral context that annotations would normally provide, leaving gaps in understanding error handling or side effects.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema fully documents all parameters. The description adds no additional parameter semantics beyond what's in the schema (e.g., it doesn't clarify 'column' index format or 'count' limits). Baseline 3 is appropriate when schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('insert one or more blank columns') and the effect ('shifting existing columns right'), which distinguishes it from sibling tools like delete_columns or copy_range. However, it doesn't explicitly differentiate from insert_rows, which performs a similar operation on rows rather than columns.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives like delete_columns, copy_range, or insert_rows. It lacks context about prerequisites (e.g., file must exist) or typical scenarios (e.g., adding space for new data).

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/marekrost/mcp-server-spreadsheet'

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