Skip to main content
Glama

insert_rows

Insert new rows into a spreadsheet at a specified position, with control over the number of rows added.

Instructions

Insert rows at the given position.

Args: sheet: Sheet index (0-based) row: Row number where new rows are inserted (1-based) count: Number of rows to insert

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sheetYes
rowYes
countNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It fails to mention whether rows are shifted down, the impact on cell references, limits, or error conditions. The description only defines parameters, missing key behavioral details for a mutation tool.

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?

The description is concise with no extraneous text. It follows a structured docstring format, listing each parameter with a brief explanation. It could be slightly more efficient by combining sentences.

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?

The description covers the basic input parameters but lacks information about output or side effects (despite an output schema existing). It does not address validations, edge cases, or interaction with sibling tools, leaving gaps for an AI agent to infer.

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?

The description adds meaning beyond the schema: it explains sheet index is 0-based, row is 1-based, and count defaults to 1. However, it does not clarify whether insertion occurs before or after the specified row, leaving slight ambiguity.

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 'Insert rows at the given position' with parameters specifying sheet, row, and count. This is a specific verb-resource-action combination that distinguishes it from sibling tools like 'delete_rows'.

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?

No guidance on when to use this tool versus alternatives (e.g., insert_columns or add_sheet). No prerequisites or context for invocation are mentioned.

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/yolonir/ironcalc-mcp'

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