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

grp-docx-mcp

by Arvindh95Censof
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

restart_numbering

Restart list numbering from a specified starting number for a selected paragraph, overriding the current continuation.

Instructions

Restart list numbering at a paragraph. Adds lvlOverride with startOverride.

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>"
    },
    "name": "restart_numbering"
  }
}

Input Schema

NameRequiredDescriptionDefault
levelNo
startNo
para_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.7.4

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries full burden. It discloses internal behavior (adding lvlOverride with startOverride) which provides some transparency. However, it does not mention side effects, data loss, or permission requirements. No contradiction with annotations since none exist.

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?

Two sentences, short and front-loaded with the main action. The structure is efficient, though additional details could be added without losing conciseness.

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 the complexity of list numbering, the description is minimal. While output schema exists to explain return values, the description lacks context on when to restart numbering (e.g., after promoting/demoting items) and does not address edge cases.

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 description coverage is 0%, so the description must compensate. It only hints that 'start' is the startOverride value and 'level' is the override level, but does not explicitly explain each parameter or provide syntax, leaving the agent to infer.

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 the tool restarts list numbering at a paragraph and specifies it adds lvlOverride with startOverride. It distinguishes from siblings like suppress_numbering or demote_list_item by focusing on restarting the numbering sequence rather than disabling or changing levels.

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 explicit guidance on when to use this tool versus alternatives such as suppress_numbering, demote_list_item, or create_multilevel_list. The description does not mention prerequisites (e.g., paragraph must be in a list) or when not to use it.

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