Pressmark

Preview Document as PNG

preview_document

Read-onlyIdempotent

Render a high-resolution 144-PPI PNG preview of the document as a Base64 Data URI for immediate visual inspection in chat.

Input Schema

Name	Required	Description
`to`	Yes	Recipient, buyer, client, or tenant counterparty details.
`from`	Yes	Issuer, seller, landlord, or service provider party details.
`items`	No	Billable line items, milestones, rent schedules, or fee breakdowns.
`notes`	No	Customer-facing notes, remittance instructions, or project context.
`terms`	No	Payment terms, late fee policy, or governing legal clauses.
`theme`	No	Preset visual typography and color theme.
`title`	No	Optional custom document heading override (e.g., 'TAX INVOICE' or 'RESIDENTIAL LEASE AGREEMENT').
`is_paid`	No	Whether the document is marked PAID IN FULL.
`currency`	No	Currency symbol or ISO code (default '$', supports 'USD', 'EUR', 'GBP', 'CAD', 'AUD', 'JPY').
`doc_type`	Yes	The archetype or category of document to synthesize (e.g., invoice, invoice_freelance, estimate, receipt, credit_note, agreement, nda, residential_lease, commercial_nnn_lease).
`due_date`	No	Payment due date or expiration date in YYYY-MM-DD format.
`tax_rate`	No	Percentage tax rate applied to subtotal (e.g., 8.25 for 8.25%).
`doc_number`	No	Unique document or invoice identifier (e.g., 'INV-2026-0042'). Auto-generated with archetype prefix when omitted.
`issue_date`	No	Document issue date in YYYY-MM-DD format.
`payment_link`	No	Optional HTTPS checkout URL (e.g., Stripe Payment Link) embedded as a clickable link and vector QR code.
`primary_color`	No	Custom primary brand hex color (e.g., '#4f46e5').
`discount_amount`	No	Document-level flat discount subtracted before grand total.
`payment_qr_code`	No	When true and payment_link is provided, embeds a vector SVG QR code for 1-scan mobile checkout.

Output Schema

Name	Required	Description	Default
`image_data_uri`	Yes	Base64 PNG data URI (data:image/png;base64,...).
`compile_time_ms`	Yes	Raster preview latency in milliseconds.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 25, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so the safety profile is covered. The description adds genuine behavioral context beyond that: 144-PPI resolution, PNG encoding, and Base64 Data URI return format, which tells the agent exactly what comes back and that it is display-ready.

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 well-formed sentence with the format and purpose front-loaded; nothing is wasted and it reads immediately.

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

Completeness4/5

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

With an output schema, full annotation coverage, and complete parameter descriptions, the description only needs to convey the render target and format, which it does. The one missing element is explicit routing against generate_document, which keeps it from a 5.

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?

Schema description coverage is 100%, so all 18 parameters are already documented in the schema, including nested party objects and enums. The description adds no parameter-specific meaning, so the baseline 3 applies.

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?

States a specific verb (Render) and resource (document as PNG preview) with the output format (Base64 Data URI) and intended use (visual inspection in chat). Distinguishes itself from generate_document by its preview purpose, though it never names that sibling explicitly.

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?

The phrase 'for immediate visual inspection in chat' implies a preview-time use case, but there is no explicit when-to-use versus generate_document or convert_document, and no exclusions or prerequisites. 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.

All Pressmark tools Inspect

Try in Browser

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

Glama MCP Gateway

Add one secure layer between your agents and this server.