Skip to main content
Glama
mort-lab

Excel MCP Server

by mort-lab

format_alignment

Apply horizontal and vertical alignment, text wrapping, and rotation to a range of cells in an Excel workbook.

Instructions

Apply alignment formatting to a range of cells.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
workbook_pathYesPath to the Excel workbook
sheet_nameYesName of the worksheet
range_refYesRange to format (e.g., 'A1:B10')
horizontalNoHorizontal alignment ('left', 'center', 'right')
verticalNoVertical alignment ('top', 'center', 'bottom')
wrap_textNoEnable text wrapping
text_rotationNoText rotation angle (0-180)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior2/5

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

With no annotations, the description should disclose behavioral traits like file modification, permission needs, or side effects. It only states 'Apply alignment formatting,' omitting that it modifies the workbook, the effect of null parameters, and potential errors.

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 sentence that front-loads the core purpose with no wasted words. Every part earns its place, making it highly efficient.

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?

Despite having an output schema, the description lacks essential context for a 7-parameter tool: no mention of mutation, return behavior, or what happens with omitted optional parameters. Sibling tools are similar, requiring clearer differentiation.

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% with detailed parameter descriptions, so the baseline is 3. The tool description adds no additional meaning beyond what the schema already 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 uses a specific verb ('Apply') and resource ('alignment formatting') to a defined scope (range of cells). It clearly distinguishes from sibling formatting tools like format_border, format_fill, etc., which apply different formatting types.

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 provided on when to use this tool versus alternatives. There is no mention of prerequisites, context, or exclusions. The agent receives no help in deciding between this and other formatting tools.

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/mort-lab/excel-mcp'

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