Skip to main content
Glama

pdf_to_xlsx

Convert PDF documents to XLSX by extracting tables on a best-effort basis.

Instructions

Converts a PDF document to XLSX format by using best effort table extraction.

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>",
      "output": "<output>"
    },
    "name": "pdf_to_xlsx"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYesThe input PDF file path.
outputYesThe output file path.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/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. 'Best effort table extraction' is a genuinely useful caveat that warns output may be imperfect or incomplete, but the description says nothing about overwriting an existing output file, permission requirements, multi-page handling, scanned/image PDFs, or what happens when no table is detected.

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 the key limitation front-loaded at the end, and no filler. It is appropriately sized, though it is thin enough that it leaves several practical questions unanswered.

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

Completeness3/5

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

For a two-parameter conversion tool with no annotations and no output schema, the agent still cannot tell what is returned (a path, a status, raw bytes) or how failures and table-less PDFs are surfaced. The description is minimally viable but omits failure and return behavior entirely.

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%, with both 'input' and 'output' documented as file paths, so the baseline is 3. The description adds no further meaning about path constraints, relative vs absolute paths, or whether the output directory must already exist.

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 both resource formats: converts a PDF into XLSX. The target format itself separates it from siblings such as pdf_to_docx, pdf_to_json, and pdf_to_markdown, but it never names an alternative or clarifies why XLSX rather than, say, JSON or CSV output.

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 when-to-use or when-not-to-use guidance. The agent gets no criteria for choosing this over pdf_to_json or pdf_to_markdown for tabular data, and no mention of prerequisites such as the PDF containing a real (non-scanned) table structure.

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