Skip to main content
Glama
zuan412

Precision PDF MCP Server

by zuan412
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
PRECISION_PDF_TEMP_DIRNoDirectory used for temporary inspector previews. If not set, the OS-standard `tempfile.gettempdir()/precision_pdf` is used.

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
}

Tools

Functions exposed to the LLM to take actions

NameDescription
hpe_inspect_virtual_gridB

Generate a temporary Virtual Excel Grid Inspector Image with Set-of-Marks (SoM) slot badges. This image overlays:

  • Top Excel column letters (A, B, C...)

  • Left Excel row numbers (1, 2, 3...)

  • Labeled slot pill badges: [S01], [S02], [S03]... on every detected blank, underline, or box. Returns JSON containing:

  • inspector_image_path: Path to the image (view it via view_file to visually inspect the layout!)

  • slots: Catalog of detected slots with tag, type, baseline, and Excel grid address (e.g. Col K, Row 9). NOTE: This is strictly a virtual guide for the agent's eyes; it does NOT alter the PDF!

hpe_fill_slotsA

Inject answers into the PDF using Slot IDs (e.g. {"S01": "answer", "S02": "B"}). Guarantees:

  • 100% baseline snap on printed lines (zero floating text).

  • 100% center alignment in boxes (zero off-center boxes).

  • Automatic multi-line wrapping across consecutive lines for long answers.

  • Automatic font scaling to avoid text collision or overflow.

  • 100% CLEAN OUTPUT: Final PDF contains ONLY answers (zero grid lines, zero badges). Args: pdf_path: Path to target PDF. page_number: 1-based page number. slot_answers_json: JSON string mapping slot tags to answers: e.g. '{"S01": "went", "S02": ["line 1 text", "line 2 text"], "circle_option": "A"}'

output_path: Optional output path. If omitted, overwrites safely via atomic replace. Returns status JSON with saved path.

hpe_render_clean_verifyB

Render the final, clean PDF page (with answers, WITHOUT any grid or badges) to a high-resolution PNG image for visual QA before submission.

hpe_inspect_geometryC

Backward compatibility alias for hpe_inspect_virtual_grid.

hpe_snap_fillC

Backward compatibility alias for hpe_fill_slots.

hpe_render_verifyC

Backward compatibility alias for hpe_render_clean_verify.

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

B3.1/5.0

Scored across 6 tools

Disambiguation2/5

Three of the six tools (hpe_inspect_geometry, hpe_snap_fill, hpe_render_verify) are explicit backward-compatibility aliases that duplicate hpe_inspect_virtual_grid, hpe_fill_slots, and hpe_render_clean_verify respectively. An agent faces real ambiguity about which name to call, even though the descriptions confess the aliasing. Only three genuinely distinct purposes exist.

Naming Consistency5/5

Every tool uses the same hpe_ prefix and snake_case verb_noun convention (render_clean_verify, inspect_virtual_grid, fill_slots, inspect_geometry, snap_fill, render_verify). The pattern is predictable throughout with no style mixing.

Tool Count3/5

Six tools nominally sits in a healthy range, but half are redundant aliases, leaving an effective surface of only three distinct operations. That makes the set feel thin for the scope despite the raw count looking fine.

Completeness4/5

The core lifecycle is covered: inspect the virtual grid to find slots, fill slots with answers, and render a clean page for visual QA. Minor gaps exist (no PDF text extraction or batch/multi-page handling), but the primary workflow has no dead ends.

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources