Skip to main content
Glama
GhazwaPasha

Google Workspace MCP Server

by GhazwaPasha

sheets_update_borders

Set borders on a range of cells in Google Sheets by specifying sheet, row/column range, sides, style, color, and width.

Instructions

Set cell borders. sides: top, bottom, left, right, innerHorizontal, innerVertical.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
colorNo#000000
sidesYes
styleNoSOLID
widthNo
end_colYes
end_rowYes
sheet_idYes
start_colYes
start_rowYes
spreadsheet_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior1/5

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

No annotations are present, so the description carries the full burden. It does not disclose whether existing borders are overwritten, how the range is interpreted, or any side effects. This is a significant gap 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.

Conciseness5/5

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

The description is extremely concise, with the action front-loaded in the first sentence and the side enumeration in the second. Every word is purposeful, and there is no redundancy.

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?

With 10 parameters and no schema descriptions, the description only explains one parameter (sides). It does not explain how to specify the range, what happens to existing formatting, or how this relates to other sheet formatting tools. The output schema existing does not compensate for missing invocation details.

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?

The description adds critical allowed values for the 'sides' parameter (top, bottom, left, right, innerHorizontal, innerVertical), which is not in the schema. However, it does not clarify other parameters like color, style, width, or the range fields.

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 cell borders' clearly identifies the action and resource. Listing sides (top, bottom, left, right, innerHorizontal, innerVertical) further distinguishes this from sibling tools like sheets_format_cells.

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 is given on when to use this tool versus alternatives such as sheets_format_cells or sheets_batch_update. There are no exclusions, prerequisites, or explicit context provided.

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/GhazwaPasha/Google-wrk-spc-mcp'

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