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

grp-docx-mcp

by Arvindh95Censof
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

sort_table

Sort table rows by column content, preserving header rows. Specify table index, column index, and sort order.

Instructions

Sort the non-header rows of a table by the text content of a column.

Header rows (marked with w:tblHeader) remain at the top. Rows with a missing cell at column_index sort as empty string.

Args: table_idx: 0-based table index. column_index: 0-based column to sort by. ascending: True for A→Z (default), False for Z→A.

Returns: {"sorted_rows": int, "column_index": int, "ascending": bool}

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_idx": "<table_idx>",
      "column_index": "<column_index>"
    },
    "name": "sort_table"
  }
}

Input Schema

NameRequiredDescriptionDefault
ascendingNo
table_idxYes
column_indexYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.7.4

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description carries full burden. It explains header rows remain at top and missing cells sort as empty string. However, it does not disclose whether the tool modifies the document in place, performance implications, or permissions required, which are important 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 concise: a brief introductory sentence, a bulleted list for arguments, and a return format. Every sentence is valuable with no redundancy. Front-loaded with key purpose.

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

Completeness4/5

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

Given the tool's simplicity and that an output schema exists, the description covers behavior (headers, missing cells), parameter details, and return format. It is mostly complete but lacks an explicit statement about whether the sort modifies the document, which is a minor gap.

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

Parameters4/5

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

Schema coverage is 0%, meaning the input schema lacks parameter descriptions. The description compensates by explaining each parameter: table_idx is 0-based, column_index is 0-based, ascending sorts A→Z or Z→A. This adds significant meaning beyond the schema.

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 'Sort the non-header rows of a table by the text content of a column.' It specifies the verb (sort), resource (non-header rows of a table), and distinguishes from sibling tools like add_table_row or delete_table_row.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implicitly defines when to use the tool (when sorting a table by a column), but does not explicitly state when not to use it or mention alternatives. Given the long list of sibling tools, explicit guidance is missing, making it average.

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