TruePath PDF MCP Server

Render pages to images

to_images

Convert PDF pages to PNG or JPG images at a specified DPI for previews, OCR, or vision model input.

Rasterize PDF pages as PNG or JPG at a chosen DPI. Useful for previews, OCR pipelines, or feeding pages back to a vision model.

TableJSON Schema

Name	Required	Description
`dpi`	No	Render resolution. Default 150. PDF native is 72; common values: 96 screen, 150 print preview, 300 print.
`path`	Yes	Absolute path to the source PDF.
`pages`	No	1-based page range, e.g. "3", "1-5", "1,3,5-7". Omit for all pages.
`format`	No	Output format. Default "png". "jpg" is smaller but lossy.
`basename`	No	Stem for output filenames. Default = source filename without .pdf. Final names: '<basename>-001.png' (page number padded to 3 digits).
`outputDir`	Yes	Directory to write the rendered images into.
`jpgQuality`	No	JPEG quality 40-100. Default 85. Ignored for PNG.

A3.9/5.0

Behavior3/5

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

Covers basic behavior but lacks disclosure of potential slowness, memory use, or file creation details beyond what schema provides.

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?

Two sentences with no fluff; use cases are front-loaded and relevant.

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?

Adequate for a tool with detailed schema, but misses context on output file creation and page range interpretation beyond schema.

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

Parameters3/5

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

Description adds little beyond schema which already has detailed parameter descriptions (100% coverage).

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?

Clearly states it rasterizes PDF pages to PNG or JPG at chosen DPI, distinguishing from siblings like extract_text and extract_images.

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

Usage Guidelines4/5

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

Mentions specific use cases (previews, OCR, vision model) and implies alternatives via sibling context, but no explicit when-not-to-use.

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

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/JoyTruepath/truepath-pdf-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server