Skip to main content
Glama

Convert PDF to Excel

pdf_to_excel
Idempotent

Turn the tables in a PDF into Excel, each in its own sheet and with numbers as numbers, ready to add up. Returns a link to download the result (kept about an hour). Credits on paid plans: 5 per page.

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": {
      "files": "<files>"
    },
    "name": "pdf_to_excel"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoLanguage. Language of the texts the tool adds. Values: 'es' = Spanish; 'en' = Englishes
filesYesInput files (.pdf). Each one is a public http(s) URL, or an object with `url`, or with `name` and `content_base64` (small files only: up to 20 MB in total).
contentNoWhat to put in Excel Values: 'tablas' = Just the tables, one sheet per table; 'todo' = All the text, one sheet per pagetablas

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

The annotations already establish that this is a non-destructive, idempotent, open-world write operation, so the lower bar applies. The description adds genuinely new details the agent cannot see elsewhere: the result arrives as a download link, that link expires after about an hour, and paid plans are charged 5 credits per page.

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?

Two tight sentences deliver the core action first, then the output, retention window and cost. No filler or repetition, and the most decision-relevant facts are 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?

With no output schema, the description usefully fills in the return format and retention window, and the cost signal supports planning. It leaves out anything about failure handling in malformed PDFs, but for a three-parameter conversion tool the gap is minor.

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 explanation of `files`, `lang` and the `content` enum is already complete in the schema. The description adds only marginal meaning beyond that by implying the default table-per-sheet behavior, and it never mentions the 'todo' (all text) option that the `content` parameter exposes.

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 ('Turn the tables in a PDF into Excel') and adds detail about fidelity ('each in its own sheet', 'numbers as numbers'), which clearly separates it from unstructured siblings like pdf_to_word. It does not explicitly name an alternative tool, so it stops short of a 5.

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

Usage Guidelines2/5

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

The description says what the tool does but never says when to choose it over alternatives such as pdf_to_word or ocr_pdf, and gives no prerequisites or exclusions. The phrase 'ready to add up' hints at numeric use cases, but the guidance remains implicit at best.

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