Skip to main content
Glama
Sign In
Office-MCP-Server

Office-MCP-Server

by stoyantsiparov
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

word_insert_paragraphs

Insert multiple new paragraphs after a specified paragraph ID in a .docx file. Supports tracked changes for collaborative editing.

Instructions

Insert new paragraphs after a given paraId

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>",
      "after_para_id": "<after_para_id>",
      "texts": "<texts>"
    },
    "name": "word_insert_paragraphs"
  }
}

Input Schema

NameRequiredDescriptionDefault
textsYesText content for each new paragraph, in order
file_pathYesAbsolute path to the .docx file
after_para_idYesw14:paraId to insert the new paragraphs after
track_changesNoRecord this edit as a tracked change (default: true)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden. It only states the basic action and does not disclose failure modes, file modification side effects, track_changes behavior, or reversibility. This is a mutation tool, so such details are important.

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 a single, front-loaded sentence with no wasted words. Every word contributes to the core meaning.

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 existence of word_insert_table_paragraphs, the description is ambiguous about whether this inserts into the main document body or table cells. It also does not mention the track_changes default or success/failure behavior, and there is no output schema to clarify return values.

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?

All parameters have descriptions in the schema, so the baseline is 3. The description adds no extra semantic value beyond what the schema already provides; it merely mirrors the action and the after_para_id concept.

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 action (insert), resource (new paragraphs), and location (after a given paraId). This distinguishes it from edit/delete paragraph tools.

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 a use case (inserting paragraphs after an existing paragraph found via paraId), but provides no explicit when/when-not guidance or alternatives. It does not mention that word_insert_table_paragraphs exists for table cells.

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