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

grp-docx-mcp

by Arvindh95Censof
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

insert_paragraph

Insert a new paragraph after a specified paragraph in a Word document. Provide the paragraph ID and text content, optionally set a style like Heading1 or Normal.

Instructions

Insert a new paragraph after the paragraph with the given paraId.

Args: after_para_id: paraId of the paragraph to insert after. text: Text content for the new paragraph. style: Optional paragraph style name (e.g., "Heading1", "Normal").

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": {
      "after_para_id": "<after_para_id>",
      "text": "<text>"
    },
    "name": "insert_paragraph"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes
styleNo
after_para_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.7.4

TDQS

A3.5/5.0
Behavior2/5

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

Minimal disclosure: describes insertion but no mention of side effects, error handling, or required permissions. No annotations provided to supplement.

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?

Single sentence for purpose, followed by clear argument list. No redundancy, front-loaded.

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

Completeness3/5

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

Adequate for a simple insertion tool with output schema. Lacks details on valid formats or edge cases, but sufficient for basic use.

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?

Adds meaning beyond schema: explains each parameter's role, provides style examples. Schema coverage 0%, so description carries burden.

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?

Clearly states verb 'insert' and resource 'paragraph' with specific location 'after the paragraph with the given paraId'. Distinguishes from siblings like 'insert_text' or 'add_table'.

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 vs alternatives like 'insert_text' or 'add_table'. No context on prerequisites or limitations.

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