Skip to main content
Glama

add_table

Insert structured tables into Word documents by specifying file path, dimensions, headers, and data content for organized information presentation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filePathYes
rowsYes
colsYes
headersNo
dataNo

Implementation Reference

  • Core handler function that creates a DOCX document containing a table with the specified number of rows and columns, populates it with provided data, and writes it to the filePath.
    async addTable(filePath: string, options: TableOptions): Promise<APIResponse> {
      try {
        const doc = new Document({
          sections: [{
            children: [
              new Table({
                rows: Array(options.rows).fill(0).map((_, rowIndex) => {
                  return new TableRow({
                    children: Array(options.cols).fill(0).map((_, colIndex) => {
                      const text = options.data?.[rowIndex]?.[colIndex] || '';
                      return new TableCell({
                        children: [new Paragraph({ text })],
                      });
                    }),
                  });
                }),
              }),
            ],
          }],
        });
    
        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}` };
      }
    }
  • MCP server tool registration for 'add_table', including Zod input schema validation and wrapper handler that delegates to DocumentService.addTable.
    server.tool(
      "add_table",
      {
        filePath: z.string(),
        rows: z.number(),
        cols: z.number(),
        headers: z.array(z.string()).optional(),
        data: z.array(z.array(z.string())).optional(),
      },
      async (params) => {
        const result = await docService.addTable(params.filePath, {
          rows: params.rows,
          cols: params.cols,
          headers: params.headers,
          data: params.data,
        });
        return {
          content: [
            {
              type: "text",
              text: result.success ? "表格已添加" : result.error!,
            },
          ],
          isError: !result.success,
        };
      }
    );
  • TypeScript interface defining the input parameters for the addTable function.
    export interface TableOptions {
      rows: number;
      cols: number;
      headers?: string[];
      data?: string[][];
      style?: string;
    }
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