PDF & Office Tools (Tanod)

pdfpeek: build an Excel workbook from JSON

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; a column type (string, number, integer, date, datetime, boolean, currency, percent) sets the format. Strings are always stored as text, never as formulas. 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

Input Schema

Name	Required	Description	Default
`output`	No	base64 (default): inline. url: stored for 24 hours; link, metadata.	base64
`sheets`	Yes	The sheets, in order: 1-20, each with a unique name, optional typed columns and rows (at most 50,000 cells in all).
`filename`	No	Name of the returned file (default workbook.xlsx; .xlsx is added when missing; only letters, digits, space, dot, dash and underscore are kept).

Output Schema

Name	Required	Description
`file`	No
`rows`	No
`cells`	No
`error`	No	Only on an error result: an object {code, message}, or the reason string of an x402 PaymentRequired object.
`sheets`	No
`operation`	No
`output_bytes`	No
`sheet_summary`	No
`formula_like_strings`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedOct 28, 2026

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."
```

Changed4 schema fields changedOct 12, 2026

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"
+  ]
+}

AddedOct 9, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations only give the safety profile (readOnly=false, destructive=false, idempotent=true); the description adds the operationally important facts: hard limits (20 sheets, 50,000 cells, 32,767 chars/cell, 31-char sheet names without [ ] : * ? / \), that exceeding them is a 422 and not charged, that strings are never interpreted as formulas, expected latency under 1 s, and a price of USD 0.005 with no free tier.

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?

The core action and sibling routing are front-loaded, then limits, error behavior, latency and price in a compact run of sentences. Dense but every clause carries information an agent needs; only the docs URL feels like appended boilerplate.

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?

For a single-call generation tool with a full output schema, the description covers what remains unaddressed elsewhere: quotas, failure mode and its billing implication, latency, cost, string-as-text semantics, and a docs link. Nothing needed to invoke it correctly is missing.

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 100%, so the baseline is 3; the description still adds value by spelling out the column `type` enum and clarifying that a type sets the cell number format. It repeats rather than extends most other parameter detail, so it does not push to a 5.

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?

Specific verb + resource (build a styled Excel workbook from JSON sheets, columns and rows), and it explicitly names the inverse tool (convert_excel_to_json) and the sibling for slides (build_pptx_deck). An agent can tell this apart from every other build/convert tool in the family without opening a schema.

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

Usage Guidelines4/5

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

It routes the agent explicitly: read-back goes to convert_excel_to_json, slides go to build_pptx_deck, and it documents format/limit constraints that determine whether it can be used at all. It stops short of stating when-not-to-use conditions beyond those alternatives, so it lands just under a 5.

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

All PDF & Office Tools (Tanod) tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?