Pressmark

Generate Vector PDF Document

generate_document

Read-onlyIdempotent

Generate a publication-ready vector PDF document (invoice, estimate, receipt, credit note, contract, NDA, purchase order, certificate, or real estate agreement) in under 25ms.

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
`doc_number`	Yes	Assigned or effective document number.
`pdf_base64`	Yes	Base64-encoded vector PDF bytes.
`grand_total`	Yes	Computed grand total.
`compile_time_ms`	Yes	Vector compilation latency in milliseconds.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 25, 2026

TDQS

B3.3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety and side-effect profile is covered structurally. The description adds useful behavioral context by stating the output is a vector PDF and that generation is fast (<25ms), but it does not describe return behavior, permissions, or limits beyond the schema.

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?

The description is a single front-loaded sentence that communicates the action, output format, representative document types, and a performance characteristic without any wasted text.

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?

The schema is rich and includes an output schema, so much of the calling contract is covered elsewhere. However, for a complex 18-parameter generation tool with multiple related siblings, the one-line description does not fully address when to use it versus preview_document or convert_document, nor does it explain the generated artifact lifecycle beyond 'vector PDF'.

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 well documented in the schema. The description's list of document categories overlaps with the doc_type enum but does not add new meaning about parameter usage, defaults, or relationships beyond what the schema provides.

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?

The description gives a specific verb ('Generate'), a precise output ('publication-ready vector PDF document'), and enumerates supported document types, making the core purpose unmistakable. It does not explicitly distinguish the tool from adjacent siblings such as preview_document or convert_document, which keeps it from a 5.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool versus alternatives like preview_document, convert_document, or calculate_totals. The only implied usage is that it is for creating documents, which an agent can infer from the name but not from explicit conditions or exclusions.

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.