Skip to main content
Glama

build_xlsx_workbook

Idempotent

pdfpeek: Build a styled Excel workbook from JSON sheets, columns and rows. To read a workbook back use convert_excel_to_json; for slides use build_pptx_deck. Rows are arrays or objects. Numeric types parse numeric strings; integers of 16 or more digits are stored as text to keep every digit. Send identifiers as strings with type string. Formulas are never written. At most 20 sheets, 50,000 cells, 32,767 characters per cell; sheet names of at most 31 characters without [ ] : * ? / . Over a limit is a 422 (not charged). Typically under 1 s. Price: USD 0.005. No free tier. Docs: https://tanod.dev/learn/xlsx-build-api.html

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "sheets": "<sheets>"
    },
    "name": "build_xlsx_workbook"
  }
}

Input Schema

NameRequiredDescriptionDefault
outputNobase64 (default): inline. url: stored for 24 hours; link, metadata.base64
sheetsYesThe sheets, in order: 1-20, each with a unique name, optional typed columns and rows (at most 50,000 cells in all; an object row with more keys than columns counts its keys).
filenameNoName of the returned file (default workbook.xlsx; .xlsx is added when missing; only letters, digits, space, dot, dash and underscore are kept).

Output Schema

NameRequiredDescriptionDefault
fileNo
rowsNo
cellsNo
errorNoOnly on an error result: an object {code, message}, or the reason string of an x402 PaymentRequired object.
sheetsNo
operationNo
output_bytesNo
sheet_summaryNo
formula_like_stringsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed22 schema fields changed
    • removedInput schema / $defs / XlsxColumn / properties / format / default
      Removed value: -null
    • removedInput schema / $defs / XlsxColumn / properties / format / title
      Removed value: -"Format"
    • removedInput schema / $defs / XlsxColumn / properties / header / title
      Removed value: -"Header"
    • removedInput schema / $defs / XlsxColumn / properties / type / default
      Removed value: -null
    • removedInput schema / $defs / XlsxColumn / properties / type / title
      Removed value: -"Type"
    • removedInput schema / $defs / XlsxColumn / properties / width / default
      Removed value: -null
    • removedInput schema / $defs / XlsxColumn / properties / width / title
      Removed value: -"Width"
    • removedInput schema / $defs / XlsxColumn / title
      Removed value: -"XlsxColumn"
    • removedInput schema / $defs / XlsxSheet / properties / autofilter / title
      Removed value: -"Autofilter"
    • removedInput schema / $defs / XlsxSheet / properties / columns / default
      Removed value: -null
    • removedInput schema / $defs / XlsxSheet / properties / columns / title
      Removed value: -"Columns"
    • removedInput schema / $defs / XlsxSheet / properties / freeze_header / title
      Removed value: -"Freeze Header"
    • removedInput schema / $defs / XlsxSheet / properties / name / title
      Removed value: -"Name"
    • removedInput schema / $defs / XlsxSheet / properties / rows / title
      Removed value: -"Rows"
    • removedInput schema / $defs / XlsxSheet / title
      Removed value: -"XlsxSheet"
    • removedInput schema / properties / filename / default
      Removed value: -null
    • removedInput schema / properties / filename / title
      Removed value: -"Filename"
    • removedInput schema / properties / output / title
      Removed value: -"Output"
    • removedInput schema / properties / sheets / title
      Removed value: -"Sheets"
    • removedInput schema / title
      Removed value: -"build_xlsx_workbookArguments"
    • removedOutput schema / properties / file / properties
      Removed value: -{
      -  "bytes": {
      -    "description": "Bytes.",
      -    "type": [
      -      "integer",
      -      "null"
      -    ]
      -  },
      -  "content_type": {
      -    "description": "MIME type.",
      -    "type": [
      -      "string",
      -      "null"
      -    ]
      -  },
      -  "data_base64": {
      -    "type": [
      -      "string",
      -      "null"
      -    ]
      -  },
      -  "dpi": {
      -    "type": [
      -      "integer",
      -      "null"
      -    ]
      -  },
      -  "expires_at": {
      -    "description": "UTC expiry.",
      -    "type": [
      -      "string",
      -      "null"
      -    ]
      -  },
      -  "first_page": {
      -    "type": [
      -      "integer",
      -      "null"
      -    ]
      -  },
      -  "height": {
      -    "type": [
      -      "integer",
      -      "null"
      -    ]
      -  },
      -  "last_page": {
      -    "type": [
      -      "integer",
      -      "null"
      -    ]
      -  },
      -  "name": {
      -    "type": [
      -      "string",
      -      "null"
      -    ]
      -  },
      -  "page": {
      -    "type": [
      -      "integer",
      -      "null"
      -    ]
      -  },
      -  "pages": {
      -    "type": [
      -      "integer",
      -      "null"
      -    ]
      -  },
      -  "sha256": {
      -    "description": "SHA-256.",
      -    "type": [
      -      "string",
      -      "null"
      -    ]
      -  },
      -  "url": {
      -    "description": "Public link.",
      -    "type": [
      -      "string",
      -      "null"
      -    ]
      -  },
      -  "width": {
      -    "type": [
      -      "integer",
      -      "null"
      -    ]
      -  }
      -}
    • removedOutput schema / properties / sheet_summary / items
      Removed value: -{
      -  "properties": {
      -    "cells": {
      -      "type": [
      -        "integer",
      -        "null"
      -      ]
      -    },
      -    "columns": {
      -      "type": [
      -        "integer",
      -        "null"
      -      ]
      -    },
      -    "name": {
      -      "type": [
      -        "string",
      -        "null"
      -      ]
      -    },
      -    "rows": {
      -      "type": [
      -        "integer",
      -        "null"
      -      ]
      -    }
      -  },
      -  "type": [
      -    "object",
      -    "null"
      -  ]
      -}
  2. Changed2 schema fields changed
    • changedInput schema / $defs / XlsxColumn / properties / type / description
      Previous value: -"string, number, integer, date, datetime, boolean, currency or percent. Sets the cell type and number format; a value that does not fit is a 422. Without it the type follows each JSON value."New value: +"Sets type and format; mismatches are a 422. Numeric types parse numeric strings; integers of 16 or more digits are stored as text to keep every digit. Omit to follow JSON values."
    • changedInput schema / $defs / XlsxSheet / properties / rows / description
      Previous value: -"Array rows (values by position) or object rows (values by header). A value is a string, number, boolean or null (an empty cell)."New value: +"Array rows (by position) or object rows (by header); cells: string, number, boolean or null (empty). Send identifiers as strings with type string."
  3. Changed1 schema field changed
    • changedInput schema / properties / sheets / description
      Previous value: -"The sheets, in order: 1-20, each with a unique name, optional typed columns and rows (at most 50,000 cells in all)."New value: +"The sheets, in order: 1-20, each with a unique name, optional typed columns and rows (at most 50,000 cells in all; an object row with more keys than columns counts its keys)."
  4. Changed6 schema fields changed
    • changedInput schema / properties / output / description
      Previous value: -"base64 (default): the file comes back inline as base64. url: the file is stored for 24 hours and the reply carries a download link (url, expires_at, bytes, content_type, sha256) instead of the base64, which keeps the file out of your context window."New value: +"base64 (default): inline. url: stored for 24 hours; link, metadata."
    • addedOutput schema / properties / file / properties / bytes / description
      Added value: +"Bytes."
    • addedOutput schema / properties / file / properties / content_type / description
      Added value: +"MIME type."
    • addedOutput schema / properties / file / properties / expires_at / description
      Added value: +"UTC expiry."
    • addedOutput schema / properties / file / properties / sha256 / description
      Added value: +"SHA-256."
    • addedOutput schema / properties / file / properties / url / description
      Added value: +"Public link."
  5. Changed4 schema fields changed
    • addedInput schema / properties / output
      Added value: +{
      +  "default": "base64",
      +  "description": "base64 (default): the file comes back inline as base64. url: the file is stored for 24 hours and the reply carries a download link (url, expires_at, bytes, content_type, sha256) instead of the base64, which keeps the file out of your context window.",
      +  "enum": [
      +    "base64",
      +    "url"
      +  ],
      +  "title": "Output",
      +  "type": "string"
      +}
    • addedOutput schema / properties / file / properties / expires_at
      Added value: +{
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / file / properties / sha256
      Added value: +{
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / file / properties / url
      Added value: +{
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
  6. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only supply the generic safety profile (readOnly=false, destructive=false, idempotent=true); the description goes well beyond with hard limits (20 sheets, 50,000 cells, 32,767 chars per cell, 31-char sheet names excluding [ ] : * ? / \), the 422-not-charged failure mode, ~1s latency, USD 0.005 price, no free tier, and the rule that formulas are never written. That is exactly the operator context that is missing from structured fields.

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?

Front-loaded with purpose and sibling routing before the constraint and pricing tail; nearly every sentence carries usable information. It is a dense wall of clauses in one block, and a short bulleted constraints section would scan better, but nothing is genuinely wasted.

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?

With an output schema present, return values need no explanation, and the description still covers limits, error behavior, cost, latency, and a docs link. For a 3-parameter, 1-required builder tool this is more than an agent needs to call it correctly.

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?

Schema description coverage is 100%, so the parameters are already documented, and most of the description's parameter talk (rows as arrays or objects, numeric-string parsing, 16-digit integers as text, identifiers as strings) repeats the schema's own wording. It reinforces but rarely adds syntax or defaults the schema lacks, so the baseline 3 applies.

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?

States a specific verb and resource ('Build a styled Excel workbook from JSON sheets, columns and rows') and immediately distinguishes itself from the read-back sibling convert_excel_to_json and the slides sibling build_pptx_deck. An agent can select it without opening the schema.

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 routes to alternatives by task: reading a workbook back goes to convert_excel_to_json, slides go to build_pptx_deck. The only weak spot is that it does not say when not to use it at all, but the sibling routing is concrete and actionable.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.