Skip to main content
Glama

excel_set_formula

Destructive

Set or modify a formula in any Excel cell by specifying file, sheet, cell, and formula (without =).

Instructions

Set or modify a formula in a cell

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filePathYesPath to the Excel file
sheetNameYesName of the sheet
cellAddressYesCell address (e.g., A1)
formulaYesExcel formula (without = sign)
createBackupNo
Behavior3/5

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

Annotations provide destructiveHint: true, so the agent knows it's a modification. The description adds minimal extra behavioral context beyond the annotation, such as implying overwriting. No contradiction.

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?

Single sentence is efficient and front-loads the action. No wasted words, though could include more structured context.

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

Completeness2/5

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

No output schema and no explanation of return values, edge cases (invalid sheet, invalid formula), or the effect of createBackup parameter. Missing context for safe invocation.

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?

80% schema coverage means most parameters are described in the schema. The description does not add additional meaning beyond the schema details (e.g., formula without '=' is already in schema). Baseline 3.

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 'Set or modify a formula in a cell' uses a specific verb and resource, clearly distinguishing it from sibling tools like excel_get_formula (read) and excel_update_cell (value).

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., excel_update_cell for values) or when not to use it. No mention of prerequisites or context.

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/sbraind/excel-mcp-server'

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