Skip to main content
Glama

Excel to PDF API - spreadsheet or CSV to a clean PDF table

excel_to_pdf
Read-onlyIdempotent

Turn an .xlsx or .csv file into a printable PDF table with page orientation and light grid lines. Runs on our server, files are deleted right after the call, nothing stored. Free: 25 calls/day per IP. Paid: $0.005 per call via x402 at https://radarbg.com/x402/excel-to-pdf.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "fileName": "table.csv",
      "fileContent": "SXRlbSxRdHksUHJpY2UKUGVuLDMsMS4yMApCb29rLDEsOS45MAo="
    },
    "name": "excel_to_pdf"
  }
}

Input Schema

NameRequiredDescriptionDefault
filesNoOr several files: [{fileName, fileContent (base64)}]
fileNameNoFile name with extension, e.g. report.pdf
gridLinesNoLight lines between rows
fileContentNoThe file as base64 (a data: URI is fine)
orientationNoauto, p (portrait) or l (landscape)auto

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior5/5

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

Beyond the annotations, the description discloses the execution context (runs on our server), data-retention behavior (files deleted right after the call, nothing stored), rate limits (25 calls/day per IP), and pricing with an x402 endpoint. These are exactly the operational facts an agent needs before sending a file.

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?

Three sentences, each doing work: capability first, then privacy/execution, then cost and limits. No filler and the core purpose is front-loaded.

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

Completeness4/5

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

No output schema exists, and the description still covers privacy, cost, and limits, which is substantial. It does not say what the response contains (e.g., PDF bytes vs. a link) or note size limits, a modest remaining gap for a file-in/file-out tool.

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 coverage is 100%, so the schema already documents fileName, fileContent, files, gridLines, and orientation. The description confirms orientation and grid-line behavior but adds no syntax or constraint detail beyond what the schema states; a 3 is the baseline.

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

Purpose4/5

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

The description gives a specific verb and resource: converting an .xlsx or .csv file into a printable PDF table. That direction (to PDF) inherently distinguishes it from reverse siblings like pdf_to_excel_word or pdf_to_text, though no sibling is named explicitly.

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

Usage Guidelines3/5

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

Usage is implied by the accepted input types (.xlsx/.csv) rather than stated as a condition for choosing this tool over alternatives. The pricing and rate-limit sentences tell an agent about cost, not about when this conversion is the right pick.

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.

Resources