Zovo PDF to Spreadsheet

List PDF tables

list_pdf_tables

Read-onlyIdempotent

Use this when the user wants to extract table from pdf, copy table from pdf, or inspect pdf to spreadsheet tables, before exporting: it shows each table's size, column types and first rows with no download. Does not make Excel or CSV files (use convert_pdf_tables for that), does not read scanned pages (no OCR), and handles up to 15 MB and 50 pages. Do not use for editing a PDF or for a PDF that is not a table.

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": {
      "file": "<file>"
    },
    "name": "list_pdf_tables"
  }
}

Input Schema

Name	Required	Description
`file`	Yes	The text-based PDF that holds the tables, e.g. report.pdf.
`pages`	No	Pages to read, e.g. 1-3,5. Default: every page (first 50).
`merge_tables`	No	true (default): join the last table on a page to the first on the next page only when their column count and whitespace-normalized source headers match.

Output Schema

Name	Required	Description	Default
`file`	Yes
`note`	No
`status`	No
`tables`	Yes
`warnings`	Yes
`truncated`	Yes
`page_count`	Yes
`pages_read`	Yes
`scanned_pages`	Yes
`table_details`	Yes
`other_text_rows`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 22, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds genuinely new behavior: it returns a preview with no download, does not perform OCR, is capped at 15 MB and 50 pages, and explains that merge_tables only joins tables when column counts and normalized headers match.

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 the trigger condition and dense with useful clauses, but the opening phrase 'extract table from pdf, copy table from pdf, or inspect pdf to spreadsheet tables' is repetitive keyword-style padding that could be compressed to a single clause.

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 read-only preview tool with an output schema and full schema coverage, the description covers everything an agent needs: purpose, alternative, exclusions, size/page limits, OCR limitation, and the nature of the preview result. Nothing material is missing.

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%, including the nested file object and the merge_tables matching rule, so the schema already carries the parameter meaning. The description only hints at the preview output ('first rows') and adds no syntax or defaults beyond what the schema states, which is the expected baseline.

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 ('extract table from pdf' / list each table's size, column types and first rows) and explicitly differentiates itself from the sibling by saying it does not make Excel or CSV files and naming convert_pdf_tables instead. An agent can select between the two without opening either 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?

Gives explicit trigger conditions ('when the user wants to extract/copy/inspect... before exporting'), names the alternative for the export case, and lists negative cases: no OCR on scanned pages, not for editing a PDF, not for a PDF without tables. Limits (15 MB, 50 pages) further bound applicability.

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

All Zovo PDF to Spreadsheet 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?