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

grp-docx-mcp

by Arvindh95Censof
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

insert_sequence_field

Insert a sequence field for automatic figure or table numbering in Word documents. Specify the sequence name and optionally reset the counter to restart numbering.

Instructions

Insert a SEQ (sequence) field for figure/table numbering.

Args: para_id: w14:paraId of the target paragraph. seq_name: The sequence identifier (e.g. "Figure", "Table"). reset: If True, restarts the sequence counter at 1.

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": {
      "para_id": "<para_id>",
      "seq_name": "<seq_name>"
    },
    "name": "insert_sequence_field"
  }
}

Input Schema

NameRequiredDescriptionDefault
resetNo
para_idYes
seq_nameYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.7.4

TDQS

A4.1/5.0
Behavior3/5

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

No annotations provided, so description carries the burden. It discloses that the tool inserts a field and explains parameters, but lacks details on side effects, permissions, or whether it modifies existing fields. Adequate but minimal.

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?

Concise and well-structured as a docstring with Args section. No redundant information.

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 presence of an output schema, the description covers purpose and parameters sufficiently. Could optionally mention return value, but not required since output schema exists.

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

Parameters5/5

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

Schema coverage is 0%, but description compensates fully: explains para_id (w14:paraId), seq_name (e.g., 'Figure'), and reset (restarts counter). Adds meaningful context beyond schema titles and types.

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 SEQ field for figure/table numbering, using specific verb and resource. It distinguishes from generic field insertion (insert_field) and other numbering tools like insert_caption.

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 implies usage for figure/table numbering but does not explicitly state when to use versus alternatives (e.g., insert_caption, insert_field). No exclusions or context provided.

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