Skip to main content
Glama
Sign In
PrecisionPDF-MCP

PrecisionPDF-MCP

by tobiasGuta
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

render_pdf_page

Convert a PDF page, including annotations, into a local PNG for visual review.

Instructions

Render a PDF page (including annotations) to a local PNG for visual review.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "file": "<file>"
    },
    "name": "render_pdf_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileYes
pageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses that annotations are baked into the render and that output is a local PNG, but says nothing about where the file is written, whether it overwrites, or how the caller retrieves it — significant gaps for a tool that writes to disk.

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?

A single tight sentence with the action front-loaded and no filler. Every clause (render, PDF page, annotations, local PNG, visual review) adds information.

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

Completeness2/5

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

With no annotations, no output schema, and no parameter descriptions, the definition leaves the agent unable to determine the output artifact's location or how to consume it. For a tool whose whole purpose is producing a file, that is a material omission.

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

Parameters2/5

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

Schema description coverage is 0% for two parameters, so the description must compensate. It only implies a page is rendered and never clarifies the 'file' parameter (path? identifier?) or the 'page' parameter's 1-based indexing and default. No added meaning beyond the raw schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Specific verb+resource+output: renders a PDF page to a local PNG. The parenthetical '(including annotations)' and the phrase 'visual review' differentiate it implicitly from text-oriented siblings like read_pdf_page and list_pdfs, though no sibling is named.

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

Usage Guidelines3/5

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

'for visual review' implies when to reach for this rather than read_pdf_page, but there is no explicit when-to-use statement, no prerequisites, and no named alternative. Usage is inferable rather than stated.

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