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

grp-docx-mcp

by Arvindh95Censof
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

add_internal_link

Append an internal link to a paragraph referencing a bookmark. Provide the paragraph ID, display text, and bookmark name.

Instructions

Append an internal anchor hyperlink (w:anchor) at the end of a paragraph.

Internal links reference bookmarks by name and do NOT add a relationship.

Args: para_id: w14:paraId of the target paragraph. text: Display text for the hyperlink. bookmark: Name of the bookmark to link to.

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>",
      "text": "<text>",
      "bookmark": "<bookmark>"
    },
    "name": "add_internal_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes
para_idYes
bookmarkYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.7.4

TDQS

A4.2/5.0
Behavior4/5

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

No annotations provided, so description carries full burden. It discloses key behaviors: appends at end, internal, does not add relationship. However, does not mention error handling or idempotency.

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?

Two sentences plus a bullet list. Front-loaded with main purpose. No redundant words.

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 output schema, the description covers essential info. Missing potential error conditions (e.g., missing bookmark) but overall adequate.

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 has 0% description coverage, so description must define parameters. It does so with brief but clear explanations for para_id, text, and bookmark, adding meaning beyond schema titles.

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 'Append', resource 'internal anchor hyperlink', and specifies it appends at the end of a paragraph. Distinguishes from siblings like add_hyperlink (external) and add_cross_reference.

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?

Provides some context (internal link, no relationship) but lacks explicit guidance on when to use vs alternatives like add_hyperlink or add_cross_reference. No mention of prerequisites or conditions.

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