Skip to main content
Glama
aspose-words

Aspose.Words MCP

Official
by aspose-words

set_table_alignment_all

Align a table horizontally relative to the page by specifying its index and the alignment direction.

Instructions

Align the entire table relative to the page

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
doc_idYes
table_indexYes
horizontalNoleft
Behavior2/5

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

With no annotations, the description carries full burden. It only states the basic action, omitting details about scope of effect, side effects, or whether the operation is reversible.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The description is a single concise sentence, but it lacks necessary detail. Conciseness is positive, but under-specification reduces effectiveness.

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?

Given no annotations, no output schema, and 3 parameters with 0% schema coverage, the description does not sufficiently explain the tool's behavior. Sibling tools like format_table suggest overlapping functionality not addressed.

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

Parameters2/5

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

Schema coverage is 0%, and the description adds no explanation for the three parameters (doc_id, table_index, horizontal). The horizontal parameter's possible values are not mentioned, despite a default of 'left'.

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 tool aligns the entire table relative to the page, using a specific verb and resource. It implicitly distinguishes from cell-level alignment tools like set_table_cell_alignment.

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., set_table_cell_alignment, format_table). No prerequisites or context are 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/aspose-words/Aspose.Words-MCP'

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