Skip to main content
Glama

generate_change_summary

Summarizes tracked changes in an open Word document into an email-ready text file for easy review of modifications.

Instructions

Summarise tracked changes already present in the open document as an email-ready .txt.

Use this after making edits with tracked=True (the default) and saving, to produce a human-readable change log of what was modified. Reads the document's existing w:ins / w:del elements, groups adjacent deletion+insertion pairs as REPLACEMENT entries, and writes a numbered list with author, date, and text per change.

Typical workflow: open_document → edit with tracked=True → save_document → generate_change_summary

If you have two separate files to compare rather than an already-edited document, use diff_to_text instead.

Args: output_path: Destination .txt path. Auto-generated from the document stem if empty. document_handle: Optional handle for concurrent session isolation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
output_pathNo
document_handleNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

No annotations provided, so description carries full burden. Describes internal details: reading w:ins/w:del elements, grouping as REPLACEMENT, outputting numbered list with author/date/text. No contradiction.

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 yet comprehensive: one-line summary, usage details, workflow, alternative, parameter descriptions. No unnecessary text.

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

Completeness5/5

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

Covers purpose, behavior, usage, parameters, and alternatives. Output schema exists so return values need not be described. Complete for this tool.

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 explains both parameters: output_path auto-generated if empty, document_handle for session isolation. Adds meaning beyond schema defaults.

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 summarizes tracked changes as an email-ready .txt file. It specifies the resource (open document) and distinguishes itself from sibling diff_to_text.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states when to use: after edits with tracked=True and saving. Provides a typical workflow and explicitly names an alternative (diff_to_text) for comparing separate files.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/SecurityRonin/docx-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server