Skip to main content
Glama

Compile and render a VDP job

fullbleed_compile_vdp
DestructiveIdempotent

Compile inline HTML/CSS and columnar variable records into one PDF, returning its path, counts, SHA-256, and compile/render metrics.

Instructions

Compile inline HTML/CSS and render columnar variable records into one PDF, returning its path, counts, SHA-256, and compile/render metrics. Releases the temporary handle after rendering. Use fullbleed_compile plus fullbleed_render_compiled when reusing a template across calls.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cssNoOptional inline print CSS; defaults to an empty stylesheet. Use @page for page size and margins. Compilation tools do not accept css_paths.
htmlYesNonempty inline static HTML. For variable records use {{slot_name}} placeholders and supply a bindings column for every slot. Compilation tools accept markup, not html_path.
modeYesfixed_bindings substitutes text while preserving compiled geometry; reflow_bindings recalculates layout and page count for variable-length content. Check pdf_profile_catalog.fixed_bindings_supported before combining fixed bindings with a PDF profile.
bindingsYesColumnar 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.
font_pathsNoExisting embeddable font files under the MCP workspace root. Register these fonts before rendering; do not rely on system fonts. Relative paths are resolved from the server's --root.
pdf_vt_jobNoOptional Job/Record/Document hierarchy and private Fullbleed DPM for pdf_profile='pdfvt1'. Omit records to generate one record and document per input, compiled copy, or binding row.
compressionNoCompression 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_pathYesDestination PDF under the MCP workspace root, relative to the server's --root. Parent directories are created; an existing file is replaced.
pdf_profileNoPDF export profile; omitted means ordinary PDF. Read fullbleed_capabilities.pdf_profile_catalog for names and font, ICC, title, and timestamp requirements. This is separate from the render tool's dev/preflight/prod preset.
document_langNoDocument language for PDF metadata, as a BCP-47 tag such as 'en-US'.
document_titleNoHuman-readable title stored in PDF metadata. Required for pdfx4 and pdfvt1 output.
document_timestampNoPDF write date: UTC YYYY-MM-DDTHH:MM:SSZ, 'current', or 'source-date-epoch' (reads SOURCE_DATE_EPOCH). Required for pdfx4 and pdfvt1. Resolved once per engine; use an explicit value for repeatable output.
output_intent_infoNoOptional human-readable description of the output condition. Requires output_intent_icc_path.
output_intent_icc_pathNoExisting ICC profile file under the MCP workspace root, used as the PDF output intent. Required by PDF/A, PDF/X, and PDF/VT profiles.
output_intent_componentsNoICC color-component count: 1 for gray, 3 for RGB, 4 for CMYK. Defaults to 3 and must match the profile supplied by output_intent_icc_path.
output_intent_identifierNoNonblank output-condition identifier for the ICC output intent; defaults to 'Custom'. Requires output_intent_icc_path.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed20 schema fields changedv2.5.2
    • 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 / 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 / css / description
      Added value: +"Optional inline print CSS; defaults to an empty stylesheet. Use @page for page size and margins. Compilation tools do not accept css_paths."
    • addedInput schema / properties / document_lang / description
      Added value: +"Document language for PDF metadata, as a BCP-47 tag such as 'en-US'."
    • changedInput schema / properties / document_timestamp / description
      Previous value: -"UTC job write date YYYY-MM-DDTHH:MM:SSZ, current, or source-date-epoch. Resolved once when the engine is created."New value: +"PDF write date: UTC YYYY-MM-DDTHH:MM:SSZ, 'current', or 'source-date-epoch' (reads SOURCE_DATE_EPOCH). Required for pdfx4 and pdfvt1. Resolved once per engine; use an explicit value for repeatable output."
    • addedInput schema / properties / document_title / description
      Added value: +"Human-readable title stored in PDF metadata. Required for pdfx4 and pdfvt1 output."
    • changedInput schema / properties / font_paths / description
      Previous value: -"Workspace-relative embeddable font paths."New value: +"Existing embeddable font files under the MCP workspace root. Register these fonts before rendering; do not rely on system fonts. Relative paths are resolved from the server's --root."
    • addedInput schema / properties / html / description
      Added value: +"Nonempty inline static HTML. For variable records use {{slot_name}} placeholders and supply a bindings column for every slot. Compilation tools accept markup, not html_path."
    • addedInput schema / properties / mode / description
      Added value: +"fixed_bindings substitutes text while preserving compiled geometry; reflow_bindings recalculates layout and page count for variable-length content. Check pdf_profile_catalog.fixed_bindings_supported before combining fixed bindings with a PDF profile."
    • addedInput schema / properties / output_intent_components / description
      Added value: +"ICC color-component count: 1 for gray, 3 for RGB, 4 for CMYK. Defaults to 3 and must match the profile supplied by output_intent_icc_path."
    • changedInput schema / properties / output_intent_icc_path / description
      Previous value: -"Workspace-relative ICC profile path."New value: +"Existing ICC profile file under the MCP workspace root, used as the PDF output intent. Required by PDF/A, PDF/X, and PDF/VT profiles."
    • addedInput schema / properties / output_intent_identifier / description
      Added value: +"Nonblank output-condition identifier for the ICC output intent; defaults to 'Custom'. Requires output_intent_icc_path."
    • addedInput schema / properties / output_intent_info / description
      Added value: +"Optional human-readable description of the output condition. Requires output_intent_icc_path."
    • 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."
    • addedInput schema / properties / pdf_profile / description
      Added value: +"PDF export profile; omitted means ordinary PDF. Read fullbleed_capabilities.pdf_profile_catalog for names and font, ICC, title, and timestamp requirements. This is separate from the render tool's dev/preflight/prod preset."
    • addedInput schema / properties / pdf_vt_job / description
      Added value: +"Optional Job/Record/Document hierarchy and private Fullbleed DPM for pdf_profile='pdfvt1'. Omit records to generate one record and document per input, compiled copy, or binding row."
    • addedInput schema / properties / pdf_vt_job / properties / id / description
      Added value: +"Nonblank part identifier, at most 4096 UTF-8 bytes. Record IDs must be unique in the job; document IDs must be unique within their record."
    • addedInput schema / properties / pdf_vt_job / properties / records / items / properties / documents / description
      Added value: +"Ordered documents in this record. Each consumes one input document, compiled copy, or binding row; final pagination supplies its page range."
    • addedInput schema / properties / pdf_vt_job / properties / records / items / properties / documents / items / properties / id / description
      Added value: +"Nonblank part identifier, at most 4096 UTF-8 bytes. Record IDs must be unique in the job; document IDs must be unique within their record."
    • addedInput schema / properties / pdf_vt_job / properties / records / items / properties / id / description
      Added value: +"Nonblank part identifier, at most 4096 UTF-8 bytes. Record IDs must be unique in the job; document IDs must be unique within their record."
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true, and idempotentHint=true, so the safety profile is covered. The description adds non-obvious lifecycle context ('Releases the temporary handle after rendering') and summarizes outputs, though the output schema already carries return values. It does not contradict the 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 front-loaded sentences with zero waste: purpose, lifecycle, then alternative routing. The output summary is brief and skimmable, earning its place without bloating the definition.

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?

For a complex 16-parameter tool with nested objects and an output schema, the description adequately covers purpose, alternative workflow, and handle lifecycle. It does not restate required parameters or PDF profile requirements, which the exhaustive schema and annotations already handle, so it is complete enough without being maximal.

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 16 parameters—including nested objects, enums, and PDF profile constraints—are fully documented in the schema. The description only briefly echoes 'inline HTML/CSS' and 'columnar variable records' without adding syntax or format detail beyond the schema, so the baseline 3 applies.

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 specific verbs ('Compile and render') and resources ('inline HTML/CSS', 'columnar variable records', 'one PDF'), and explicitly distinguishes itself from fullbleed_compile plus fullbleed_render_compiled. An agent can tell this is the one-shot VDP compile-and-render tool without opening the 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?

Gives an explicit routing rule: use this tool for one-shot compile-and-render, and use fullbleed_compile plus fullbleed_render_compiled when reusing a template across calls. The alternative is named with the condition that selects it, leaving little to inference.

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