Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
GEMINI_API_KEYNoGoogle Gemini API key for LLM extraction (required for pdfmux[llm])
GOOGLE_API_KEYNoAlternative environment variable for Gemini API key

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_pdf_metadataA

Get PDF metadata instantly — page count, file size, document type, and whether it has tables. No extraction performed. Use this first to decide which tool to call next: convert_pdf for full text, analyze_pdf for quality audit, or extract_structured for tables.

convert_pdfA

Convert a PDF to AI-readable Markdown. Automatically detects the PDF type and picks the best extraction method. Returns confidence score and warnings when extraction is limited.

analyze_pdfA

Quick PDF triage — classify type and audit page quality without full extraction. Returns page count, type detection, per-page quality breakdown, and estimated extraction difficulty. Much cheaper than convert_pdf for initial assessment.

batch_convertC

Convert all PDFs in a directory to Markdown. Returns a summary with per-file results.

extract_structuredA

Extract structured data from a PDF — tables as JSON, key-value pairs, and optionally map to a JSON schema. Returns tables with headers/rows, detected key-value pairs with auto-normalization (dates, amounts, rates), and schema-mapped output if a schema is provided.

extract_streamingA

Stream extraction events for a PDF as NDJSON.

Use for large documents (100+ pages) where waiting for the full extraction is impractical. The response body is newline-delimited JSON with one object per line:

{"type":"classified","data":{"page_count":N,"page_types":[...]}}
{"type":"page","data":{"page_num":0,"text":"...","confidence":0.92,...}}
{"type":"warning","data":{"message":"..."}}        (zero or more)
{"type":"complete","data":{"total_confidence":0.94,"ocr_pages":[...],...}}

The first event is always classified; the last is always complete. Each page event arrives as soon as that page is extracted, including OCR re-extraction in standard/high quality modes.

verify_extractionA

Audit an extraction of a PDF for silently-dropped pages — the failure where an extractor returns nothing for a page that has real text while reporting success. Pass extracted_text with another engine's output (Reducto, Mistral OCR, LlamaParse, Docling, an in-house parser — as JSON, Markdown, or plain text) to certify THAT engine against the source PDF; omit it to have pdfmux extract the document itself and certify its own read. Returns the per-page audit — each page marked usable / silently-empty / recovered / review / unverifiable — the "N of M pages silently dropped" headline, and an overall PASS/REVIEW/FAIL verdict with a tamper-evident signature. Reuses pdfmux's own audit pass as the ground truth.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.7/5.0

Scored across 7 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: metadata extraction, full conversion, quality analysis, batch processing, structured data extraction, streaming extraction, and verification. No two tools overlap in functionality, and descriptions guide selection.

Naming Consistency4/5

Tool names mostly follow a verb_noun pattern (e.g., get_pdf_metadata, convert_pdf), but batch_convert reverses the order and extract_structured/extract_streaming use adjective noun after verb. This minor inconsistency lowers the score slightly.

Tool Count5/5

Seven tools cover the core PDF extraction workflow—metadata, analysis, conversion, batch, structured extraction, streaming, and verification—without redundancy. The scope is well-balanced for the domain.

Completeness4/5

The tool set covers the main PDF processing tasks (metadata, conversion, analysis, extraction, streaming, verification) but lacks basic operations like merging or splitting. For an extraction-focused server, the coverage is very good.

Maintenance

ActivityMaintained
ResponsivenessUnresponsive