Skip to main content
Glama

generate_change_summary

Generate a human-readable summary of all tracked changes (insertions, deletions, replacements) from a Word document. Outputs a .txt file with a numbered list showing author, date, and change details.

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
Behavior4/5

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

No annotations provided, so description carries full burden. It explains the internal process: reads w:ins/w:del elements, groups pairs as REPLACEMENT, writes numbered list with author, date, text. Does not discuss performance or limits, but is sufficient for understanding behavior.

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?

Well-structured with clear sections (purpose, workflow, alternative, parameters). Front-loaded with main action. Slightly verbose but all sentences add value.

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?

Given that an output schema exists (context signals), description need not detail output. It covers prerequisites (tracked=True, save), workflow, behavior, parameter semantics, and alternative tool. Complete for the provided context.

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 description coverage is 0%, but the description adds meaning to both parameters: output_path is a destination .txt path auto-generated from document stem if empty; document_handle is optional for session isolation. This compensates well for the lack of schema descriptions.

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 verb (summarise) and resource (tracked changes already present in the open document) with a specific output format (email-ready .txt). It distinguishes from the sibling tool diff_to_text by noting that this tool works on an already-edited document, not two separate files.

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?

Provides explicit when-to-use guidance: after making edits with tracked=True and saving. Includes a typical workflow. Directs to diff_to_text when comparing two separate files, which is a clear alternative.

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/Arvindh95Censof/grp-docx-mcp'

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