Fullbleed PDF Engine

Overview Schema Source Related Servers Discussions Admin

Render a compiled document

fullbleed_render_compiled

DestructiveIdempotent

Render a compiled PDF from a session compile_id in static, fixed-binding, or reflow mode. Returns the output path, page and record counts, and SHA-256 hash for verification.

Instructions

Write a PDF from compile_id returned by fullbleed_compile in this server session. Choose static copies, fixed geometry, or content reflow; returns the output path, page/record counts, and SHA-256. Use fullbleed_compile_vdp to compile and render a variable-data job in one call.

Input Schema

TableJSON Schema

Name	Required	Description
`mode`	Yes	static repeats the compiled document using copies; fixed_bindings substitutes columnar text without changing geometry; reflow_bindings lays out variable-length records and repaginates. The binding modes require bindings.
`copies`	No	Number of identical document copies in static mode; defaults to 1. Ignored for binding modes, whose record count is the binding-column length.
`bindings`	No	Columnar records, for example {"name": ["Ada", "Lin"]}. Keys must match the compiled {{slot_name}} set exactly. Every column must be a nonempty string array of equal length; values at the same index form one record. Required for fixed_bindings and reflow_bindings; ignored in static mode.
`compile_id`	Yes	Opaque handle returned by fullbleed_compile in this same server process. Recompile if the process restarted or the handle was evicted; it is not a filename or serialized artifact.
`compression`	No	Compression strategy for reflow_bindings only; defaults to throughput. Use compact for smaller output at additional compression cost. Ignored in static and fixed_bindings modes.
`output_path`	Yes	Destination PDF under the MCP workspace root, relative to the server's --root. Parent directories are created; an existing file is replaced.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedv2.5.2Oct 2, 2026

addedInput schema / properties / bindings / description

Added value: +"Columnar records, for example {\"name\": [\"Ada\", \"Lin\"]}. Keys must match the compiled {{slot_name}} set exactly. Every column must be a nonempty string array of equal length; values at the same index form one record. Required for fixed_bindings and reflow_bindings; ignored in static mode."

addedInput schema / properties / compile_id / description

Added value: +"Opaque handle returned by fullbleed_compile in this same server process. Recompile if the process restarted or the handle was evicted; it is not a filename or serialized artifact."

addedInput schema / properties / compression / description

Added value: +"Compression strategy for reflow_bindings only; defaults to throughput. Use compact for smaller output at additional compression cost. Ignored in static and fixed_bindings modes."

addedInput schema / properties / copies / description

Added value: +"Number of identical document copies in static mode; defaults to 1. Ignored for binding modes, whose record count is the binding-column length."

addedInput schema / properties / mode / description

Added value: +"static repeats the compiled document using copies; fixed_bindings substitutes columnar text without changing geometry; reflow_bindings lays out variable-length records and repaginates. The binding modes require bindings."

addedInput schema / properties / output_path / description

Added value: +"Destination PDF under the MCP workspace root, relative to the server's --root. Parent directories are created; an existing file is replaced."

First observedOct 1, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, readOnlyHint=false, so the safety profile is largely covered. The description adds the session-bound nature of compile_id and the returned artifacts (path, counts, SHA-256), but does not itself warn that an existing output file is replaced (that detail lives in the schema). Modest added value on top of annotations.

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?

Three tight sentences: the write action and input first, the mode choice and return values second, the sibling routing last. No filler and the operative information is front-loaded.

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 present, return values need not be spelled out, yet the description briefly confirms them; the session-scoped compile_id constraint and mode selection are covered. Slightly incomplete about what 'choose' means operationally and when to prefer the non-VDP render siblings.

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 every parameter including mode, bindings, copies, and compression is already documented with enum semantics. The description's 'static copies, fixed geometry, or content reflow' merely paraphrases the enum values and adds no format or constraint detail beyond the schema. Baseline 3 is appropriate.

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?

Starts with a specific verb+resource ('Write a PDF') and immediately scopes the input to a compile_id from fullbleed_compile in the same session. This distinguishes it from fullbleed_compile, fullbleed_render, and fullbleed_render_preview without opening another schema.

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?

Explicitly routes one alternative use case ('Use fullbleed_compile_vdp to compile and render a variable-data job in one call'), which tells the agent when to prefer a sibling. It stops short of naming the conditions for the other render siblings (fullbleed_render, fullbleed_render_preview).

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

Deploy Server