Skip to main content
Glama

set_page_margins

Adjust page margins in Word documents by specifying top, right, bottom, and left values to control document layout and formatting.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filePathYes
topNo
rightNo
bottomNo
leftNo

Implementation Reference

  • The `setPageMargins` method implements the core logic for setting page margins on a document by creating a new docx Document instance with the specified margins (in twips, default 1440) and overwriting the file at filePath.
    async setPageMargins(filePath: string, margins: PageMargins): Promise<APIResponse> {
      try {
        const doc = new Document({
          sections: [{
            properties: {
              page: {
                margin: {
                  top: margins.top || 1440, // 默认 1 英寸 (1440 twips)
                  right: margins.right || 1440,
                  bottom: margins.bottom || 1440,
                  left: margins.left || 1440,
                },
              },
            },
            children: [],
          }],
        });
    
        await Packer.toBuffer(doc).then((buffer) => {
          return fs.writeFile(filePath, buffer);
        });
    
        return { success: true };
      } catch (error) {
        const err = error as Error;
        return { success: false, error: `设置页面边距失败: ${err.message}` };
      }
    }
  • Registers the 'set_page_margins' tool in the MCP server using McpServer.tool, with Zod schema for parameters and an async handler that calls DocumentService.setPageMargins.
    server.tool(
      "set_page_margins",
      {
        filePath: z.string(),
        top: z.number().optional(),
        right: z.number().optional(),
        bottom: z.number().optional(),
        left: z.number().optional(),
      },
      async (params) => {
        const result = await docService.setPageMargins(params.filePath, {
          top: params.top,
          right: params.right,
          bottom: params.bottom,
          left: params.left,
        });
        return {
          content: [
            {
              type: "text",
              text: result.success ? "页面边距已设置" : result.error!,
            },
          ],
          isError: !result.success,
        };
      }
    );
  • TypeScript interface PageMargins defining the input parameters for margins (optional numbers, units in twips). Used by the handler.
    export interface PageMargins {
      top?: number;
      right?: number;
      bottom?: number;
      left?: number;
    }
  • src/server.ts:158-165 (registration)
    In the HTTP server's tool dispatcher switch statement, handles 'set_page_margins' by calling DocumentService.setPageMargins.
    case 'set_page_margins':
      result = await docService.setPageMargins(parameters.filePath, {
        top: parameters.top,
        right: parameters.right,
        bottom: parameters.bottom,
        left: parameters.left,
      });
      break;
  • JSON schema definition for the 'set_page_margins' tool in the HTTP server, listing parameters and requirements.
      name: 'set_page_margins',
      description: '设置页面边距',
      parameters: {
        properties: {
          filePath: { type: 'string', description: '文档路径' },
          top: { type: 'number', description: '上边距' },
          right: { type: 'number', description: '右边距' },
          bottom: { type: 'number', description: '下边距' },
          left: { type: 'number', description: '左边距' },
        },
        required: ['filePath'],
        type: 'object',
      },
    },
Behavior1/5

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

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

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

Completeness1/5

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

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

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

Purpose1/5

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

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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/puchunjie/doc-tools-mcp'

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