Skip to main content
Glama

save_document

Save Microsoft Word documents to disk for persistent storage and future access. This tool stores documents with their formatting, tables, and content intact.

Instructions

Save the document to disk

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
docIdYesDocument identifier

Implementation Reference

  • The handler function for the 'save_document' tool. It calls documentManager.saveDocument with the provided docId and returns a success message with the saved filepath.
    case "save_document":
      const filepath = await documentManager.saveDocument(args.docId);
      return {
        content: [
          {
            type: "text",
            text: `Document saved successfully to: ${filepath}`,
          },
        ],
      };
  • Input schema definition for the 'save_document' tool, specifying that it requires a 'docId' string parameter.
    {
      name: "save_document",
      description: "Save the document to disk",
      inputSchema: {
        type: "object",
        properties: {
          docId: {
            type: "string",
            description: "Document identifier",
          },
        },
        required: ["docId"],
      },
    },
  • src/index.ts:24-28 (registration)
    Registers the list of available tools (from documentTools array, which includes 'save_document') with the MCP server for the ListToolsRequest.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return {
        tools: documentTools,
      };
    });
  • Core implementation of saving the document: reconstructs the DOCX from in-memory paragraphs using docx library, writes buffer to file, returns filepath.
    async saveDocument(docId: string): Promise<string> {
      const docInfo = this.getDocument(docId);
    
      // Recreate document with all paragraphs
      const document = new Document({
        sections: [
          {
            properties: {},
            children: docInfo.paragraphs,
          },
        ],
      });
    
      const buffer = await Packer.toBuffer(document);
      await fs.writeFile(docInfo.filepath, buffer);
    
      return docInfo.filepath;
    }
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It states 'Save the document to disk' but does not clarify if this is a write operation, what permissions are needed, whether it overwrites existing files, or any side effects like file format changes. This leaves critical behavioral traits unspecified.

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, clear sentence with no wasted words. It is front-loaded and efficiently conveys the core action, making it highly concise and well-structured for its simplicity.

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?

For a tool that performs a write operation (implied by 'save') with no annotations and no output schema, the description is incomplete. It lacks details on behavior, error handling, or what happens after saving (e.g., file path, confirmation). Given the complexity and missing structured data, more context is needed for effective use.

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?

The input schema has 100% description coverage, with 'docId' documented as 'Document identifier'. The description adds no additional meaning beyond this, such as explaining the format or source of the ID. Given high schema coverage, the baseline score of 3 is appropriate as the schema handles parameter documentation adequately.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the action ('Save') and resource ('the document'), which provides a basic purpose. However, it lacks specificity about what 'save' entails (e.g., overwrite, create new file, format) and does not distinguish it from sibling tools like 'create_document' or 'apply_text_formatting', making it vague in context.

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 guidance is provided on when to use this tool versus alternatives. It does not mention prerequisites (e.g., document must exist), exclusions, or comparisons to siblings like 'create_document' for new documents or 'get_document_structure' for viewing, leaving the agent with no usage context.

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/bibash44/word-documet-mcp-server'

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