Skip to main content
Glama

PDF в Excel

pdf_to_excel

Извлекает таблицы из PDF и сохраняет в Excel (.xlsx). file_url: публичный URL PDF-файла. layout: per-table (по умолчанию) | single-sheet.

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_url": "<file_url>"
    },
    "name": "pdf_to_excel"
  }
}

Input Schema

NameRequiredDescriptionDefault
layoutNoper-table
file_urlYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false, and destructiveHint=false, so the mutation and network-fetch profile is covered. The description adds genuine context beyond them: the output is a .xlsx file and the source must be a publicly reachable URL (an access/auth constraint). It omits notable behavior such as what happens with scanned PDFs or PDFs with no detectable tables.

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 one-line purpose, then two compact parameter lines with zero filler. Slightly telegraphic — the layout line is a bare enumeration rather than an explanation — but every sentence earns its place.

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?

With only 2 parameters, an output schema, and annotations covering the safety profile, the definition is close to adequate: output format and both parameters are covered. It still leaves out failure/edge-case behavior (scanned PDFs needing ocr_pdf, no-tables-found case) and any hint about the returned file reference.

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

Parameters4/5

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

Schema description coverage is 0%, so the description carries the full burden, and it documents both parameters: file_url as a public PDF URL and layout as per-table (default) vs single-sheet. That closes the coverage gap, though it does not explain what per-table vs single-sheet actually does to the resulting workbook structure.

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?

"Извлекает таблицы из PDF и сохраняет в Excel (.xlsx)" names a specific verb (extract tables) and a specific resource (PDF -> XLSX), which distinguishes it from conversion siblings such as pdf_to_word, pdf_to_txt, and pdf_to_markdown. It stops short of explicitly naming those siblings as alternatives, so it is clear but not fully differentiated.

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 never says when to pick this tool over pdf_to_word / pdf_to_markdown / ocr_pdf, nor does it state prerequisites such as the PDF needing a text-based (non-scanned) table. The only usage-adjacent hint is the "публичный URL" requirement for file_url.

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.