Skip to main content
Glama

doc.page PDF Extraction

by page.doc

extract_pdf

Extract a PDF into clean Markdown and structured elements (headings, paragraphs). Returns the canonical ExtractedDocument object. mode "hybrid" runs a heavier semantic engine that also reconstructs tables and bounding boxes; the default "fast" engine is prose-only (low confidence.tables).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYeshttp(s) URL of the PDF to extract.
modeNofast = prose engine. hybrid = semantic engine with tables + bounding boxes when deployed; falls back to fast with a warning otherwise.
outputsNoSubset of outputs to include. Default: markdown and elements.
chunkTokensNoTarget chunk size in tokens (when chunks are requested). Default 512.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed4 schema fields changed
    • changedInput schema / properties / chunkTokens / description
      Previous value: -"Tamaño objetivo de chunk en tokens (si se piden chunks). Por defecto 512."New value: +"Target chunk size in tokens (when chunks are requested). Default 512."
    • changedInput schema / properties / mode / description
      Previous value: -"fast = server-pdfjs (prosa). hybrid = server-opendataloader (tablas + bounding boxes) si está desplegado; si no, cae a fast con un warning."New value: +"fast = prose engine. hybrid = semantic engine with tables + bounding boxes when deployed; falls back to fast with a warning otherwise."
    • changedInput schema / properties / outputs / description
      Previous value: -"Subconjunto de salidas a incluir. Por defecto: markdown y elements."New value: +"Subset of outputs to include. Default: markdown and elements."
    • changedInput schema / properties / url / description
      Previous value: -"URL http(s) del PDF a extraer."New value: +"http(s) URL of the PDF to extract."
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description must carry the transparency burden. It discloses the return type (ExtractedDocument), mode differences, and fallback behavior for hybrid. However, it does not mention error handling or side effects, which is a minor gap.

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?

The description is three sentences, front-loading the core purpose and return type, then details on modes. Every sentence adds critical information with zero redundancy or fluff.

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?

Despite no output schema, the description clarifies the return value is the canonical ExtractedDocument object and lists structural elements. It lacks explanation of error conditions or input constraints like file size, but covers the main use case well.

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?

All parameters have schema descriptions (100% coverage), so the baseline is 3. The description adds significant value for the 'mode' parameter by explaining engine differences and fallback behavior, slightly elevating it above 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?

The description clearly states the tool extracts a PDF to clean Markdown and structured elements, with a specific verb ('Extract') and resource ('PDF'). It distinguishes from siblings like list_tables and get_chunks by focusing on full document extraction.

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

Usage Guidelines3/5

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

The description explains when to use fast vs hybrid mode, but it does not provide explicit guidance on when to use this tool versus alternatives like list_tables for table extraction. This lack of cross-tool comparisons leaves usage partially ambiguous.

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

All doc.page PDF Extraction toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.2/5.0
Disambiguation5/5

Each tool targets a distinct operation: PDF extraction, table extraction, chunking, link creation, listing, stats, and revocation. No overlapping purposes.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern with lowercase and underscores, e.g., create_doc_link, extract_pdf, list_tables.

Tool Count5/5

Seven tools is an appropriate scope for a PDF extraction and link management server, covering both processing and lifecycle operations without excess.

Completeness4/5

Covers core extraction (text, tables, chunks) and link management (create, list, stats, revoke). Minor gap: no update operation for doc links, but not critical.

Resources