Skip to main content
Glama
Wildebeest

MCP PDF Forms

by Wildebeest
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

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

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
list_pdfsB
List PDF files in configured base paths

Args:
    path_filter: Optional string to filter PDF paths

Returns:
    List of PDF paths matching the filter
extract_form_fieldsC
Extract all form fields from a PDF

Args:
    pdf_path: Path to the PDF file

Returns:
    Dictionary of form field names and their properties
highlight_form_fieldA
Generate an image with the specified form field highlighted with a red box

Args:
    pdf_path: Path to the PDF file
    field_name: Name of the form field to highlight

Returns:
    Image of the page with the field highlighted
render_pdf_pageB
Generate an image of a PDF page without any highlighting

Args:
    pdf_path: Path to the PDF file
    page_num: Page number to render (0-indexed)
    zoom: Zoom factor for rendering (higher values for better quality)
    
Returns:
    Image of the specified page
extract_textA
Extract text from PDF pages

Args:
    pdf_path: Path to the PDF file
    start_page: Page number to start extraction (0-indexed). If None, starts from first page.
    end_page: Page number to end extraction (0-indexed, inclusive). If None, ends at start_page if specified, otherwise extracts all pages.
    
Returns:
    If extracting a single page: string containing the page text
    If extracting multiple pages: dictionary mapping page numbers to page text
search_textA
Search for text pattern in a PDF file

Args:
    pdf_path: Path to the PDF file
    pattern: Regular expression pattern to search for
    case_sensitive: Whether to perform case-sensitive matching
    start_page: Page number to start search (0-indexed). If None, starts from first page.
    end_page: Page number to end search (0-indexed, inclusive). If None, searches all pages.
    
Returns:
    List of matches with page number, match text, and context

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.8/5.0

Scored across 6 tools

Disambiguation5/5

Each tool has a clearly distinct purpose with no ambiguity. extract_form_fields handles form-specific metadata, extract_text retrieves raw text, highlight_form_field visually marks form fields, list_pdfs enumerates files, render_pdf_page generates page images, and search_text performs pattern matching. The descriptions reinforce these unique roles, making tool selection straightforward.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern with snake_case, such as extract_form_fields, highlight_form_field, and render_pdf_page. The naming is predictable and readable throughout, with no deviations or mixed conventions, enhancing clarity and usability.

Tool Count5/5

With 6 tools, the server is well-scoped for PDF form and content processing. Each tool earns its place by covering distinct aspects like extraction, rendering, listing, and searching, without being overly sparse or bloated. This count aligns well with the domain's typical operations.

Completeness4/5

The tool set provides strong coverage for PDF form and text operations, including extraction, rendering, listing, and searching. A minor gap exists in form field modification (e.g., fill_form or update_form_field), but agents can work around this by using other tools or external methods. Core workflows are well-supported.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources