Skip to main content
Glama
xsnj-9527

docs-mcp

by xsnj-9527
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Render a PDF page as an image

pdf_render_page
Read-only

Render a single PDF page as an image to view scanned content, diagrams, tables, or equations that plain text cannot convey.

Instructions

Render one page of a PDF as an image and return it for you to look at.

This is how you read a scanned PDF, and how you see anything that plain text cannot carry: figures, block diagrams, circuit drawings, tables, equations, page layout, handwriting.

The rendered page is returned as an actual image, so you see exactly what is on it.

Options:

  • scale zooms. Omit it and the page is rendered at a width that keeps body text legible. Use 2–3 when small text or a dense diagram matters.

  • region renders only part of the page, as fractions of the page from the top-left, e.g. {x:0.5,y:0.1,w:0.5,h:0.3} for the top-right quadrant. Combine with a larger scale to zoom into one figure or equation. Prefer this over rendering a whole page at a huge scale, which wastes the image budget on whitespace.

  • out_path also writes the PNG to a file, when you need an artifact on disk.

To read a run of pages, call this once per page. Do not try to read a 400-page book end to end: use pdf_outline to find the relevant section and render only those pages.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageYesPage to render, 1-based.
pathYesPath to the PDF.
scaleNoZoom factor. Omit for an automatic width that keeps body text legible.
regionNoRender only part of the page, as fractions from the top-left.
out_pathNoAlso write the PNG here.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.9/5.0
Behavior5/5

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

Annotations cover the safety profile (readOnly, non-destructive), and the description adds genuine behavioral context beyond them: the return value is an actual image the agent inspects, rendering consumes an image budget, wasteful full-page high-scale renders should be avoided, and out_path produces an on-disk side effect. It also sets the calling pattern ('once per page').

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?

Front-loaded with the core action, then a bulleted options list and a closing workflow rule. Every sentence carries information; no repetition of the name or restatement of the schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 5-parameter nested-schema tool with no output schema, the description fully covers what is returned (an image), how to control zoom and cropping, the file-writing side effect, and the multi-page strategy. Nothing an agent needs in order to call it correctly is missing.

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?

Schema coverage is already 100%, but the description still adds real meaning: scale omission gives an auto width tuned for legibility, a recommended 2–3 range, a concrete region example with quadrant semantics and fractional-from-top-left coordinates, and guidance to combine region with scale. It stops short of documenting coordinate edge cases, but adds clear value over the schema.

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?

States a specific verb and resource ('Render one page of a PDF as an image') and immediately contrasts with text extraction by naming the cases plain text cannot carry: scans, figures, equations, handwriting. An agent can distinguish this from pdf_read or pdf_info without opening a schema.

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

Usage Guidelines5/5

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

Explicit about when to use it (scanned PDFs, visual content), when to zoom via scale 2–3, when to prefer region over whole-page rendering, and when NOT to use it ('do not try to read a 400-page book end to end: use pdf_outline'). Names the sibling alternative directly.

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

Deploy Server

Other Tools