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

docx-mcp-server

by knorq-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

insert_table

Insert a table at a specified position in a .docx file with custom rows, columns, and optional cell values.

Instructions

Insert a table at a specific position in the document.

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": {
      "file_path": "<file_path>",
      "position": "<position>",
      "rows": "<rows>",
      "cols": "<cols>"
    },
    "name": "insert_table"
  }
}

Input Schema

NameRequiredDescriptionDefault
file_pathYesAbsolute path to the .docx file
positionYesBlock index to insert before (-1 for end)
rowsYesNumber of rows
colsYesNumber of columns
dataNoOptional 2D array of cell values, e.g. [['A1','B1'],['A2','B2']]

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.1.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations provided, and the description does not disclose behavioral traits such as whether the table overwrites existing content, shifting of text, permissions required, or side effects.

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?

Extremely concise single sentence, but lacks any structured detail. Could benefit from a second sentence explaining the position parameter or data usage.

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 no output schema and 5 parameters, the description is too minimal. It doesn't explain the return value, how the position index works, or how data is used. Not complete for effective use.

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%, so baseline is 3. The description adds minimal extra meaning beyond the schema (only 'at a specific position' is slightly redundant with the position parameter description).

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 clearly states it inserts a table at a specific position in a document, using a specific verb and resource. It distinguishes from siblings like edit_table_cells or insert_paragraphs.

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 like insert_paragraphs or edit_table_cells. No conditions or exclusions mentioned.

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