Skip to main content
Glama
Sign In
grp-docx-mcp

grp-docx-mcp

by Arvindh95Censof
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

merge_cells

Merge a rectangular range of cells in a Word document table by specifying the table index and start/end row and column coordinates.

Instructions

Merge a rectangular range of cells. Horizontal: gridSpan. Vertical: vMerge.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "table_index": "<table_index>",
      "start_row": "<start_row>",
      "start_col": "<start_col>",
      "end_row": "<end_row>",
      "end_col": "<end_col>"
    },
    "name": "merge_cells"
  }
}

Input Schema

NameRequiredDescriptionDefault
end_colYes
end_rowYes
start_colYes
start_rowYes
table_indexYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.7.4

TDQS

C2.1/5.0
Behavior2/5

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

No annotations provided, so description carries full burden. It does not disclose what happens to cell content, whether the operation is destructive, or any other behavioral traits.

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 short (two sentences) but lacks structure and leaves many details unaddressed. It could be more concise while adding necessary clarification.

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

Completeness1/5

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

With 5 required parameters, no parameter descriptions, and an output schema, the description is highly incomplete. It does not explain the tool's behavior in the context of a table or how to use it effectively.

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

Parameters1/5

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

Schema coverage is 0% with no parameter descriptions. The description does not explain how the five integer parameters (table_index, start_row, start_col, end_row, end_col) define the range or how 'gridSpan' and 'vMerge' relate to them.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it merges a rectangular range of cells, but the mention of 'gridSpan' and 'vMerge' is ambiguous without context. It distinguishes from siblings by being the only merge tool, but lacks specificity about the merge action.

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. The description does not mention prerequisites or context for merging cells.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools