Skip to main content
Glama

pdf_extract_tables

Extract tabular data from PDF files and save it as JSON or CSV for analysis, reporting, or data migration.

Instructions

Extract tabular data from PDF into JSON or CSV

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": {
      "input": "<input>"
    },
    "name": "pdf_extract_tables"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYes
formatNo
outputNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden and discloses almost nothing: no word on scanned/image PDFs, OCR, encrypted files, table detection limits, or where the 'output' goes. Only the output formats (JSON or CSV) are disclosed, which is the bare minimum.

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?

A single tight sentence with no filler, and the formats are front-loaded. Brevity is not the problem here — the gap is that so little is said.

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

Completeness2/5

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

With zero annotation coverage, no output schema, and 0% parameter documentation, an agent cannot reliably construct a call or predict the result shape. The description should at least document the input/output parameters and clarify scanned-PDF behavior.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must compensate and largely fails: 'JSON or CSV' hints at the 'format' parameter, but 'input' and 'output' are never explained (file path? base64? directory?). Two of three parameters remain semantically undefined.

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 states a specific verb and resource ('Extract tabular data from PDF') plus the two output forms, which clearly separates it from siblings like pdf_extract_text and pdf_extract_images. It stops short of referencing those siblings explicitly, but the resource is unambiguous.

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?

There is no guidance on when to choose this over pdf_extract_text or pdf_extract_patterns, and no mention of prerequisites such as text-based vs scanned PDFs. An agent must infer the selection criteria from the name alone.

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