Skip to main content
Glama
Nizoka

pdfnative-mcp

Add table / report

add_table
Idempotent

Generate a PDF report from column headers and data rows. Produce tabular PDFs for exports, summaries, and schedules with customizable options.

Instructions

Generate a tabular PDF report from column headers and data rows. Ideal for data exports, financial summaries, schedules. Smart-table fields (pdfnative v1.2) automatically engage the document backend: wrap (auto/always/never), repeatHeader (header row on every page), zebra (alternate-row tint), caption (above the table, tagged for PDF/A), minRowHeight (points), cellPadding (points). Every row must have the same length as headers. For PDF/A output, set pdfA="pdfa2b" (most compatible).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pdfANoOptional PDF/A conformance level (powered by pdfnative v1.2). Use 'pdfa1b' for archival of simple text+images, 'pdfa2b'/'pdfa2u' for richer content (2u guarantees Unicode mapping), 'pdfa3b' when embedding source attachments (Factur-X / ZUGFeRD). Mutually exclusive with PDF encryption. See docs/guides/PDFA.md.
rowsYesData rows. Each row is an array of cell strings with the same length as `headers`.
wrapNoCell wrap policy (pdfnative v1.2). 'auto' (default) wraps only when a cell overflows; 'always' wraps every cell; 'never' uses v1.1 character truncation.
titleYesReport title rendered at the top of the document and used as PDF metadata title.
zebraNoEnable zebra striping (alternate-row light tint, PDF/A-1b safe). pdfnative v1.2.
captionNoCaption rendered above the table (and emitted as /Caption structure element in tagged/PDF/A mode). pdfnative v1.2.
headersYesColumn header labels. Must have the same length as each row in `rows`.
clipCellsNoWhen true, cell contents are clipped to column bounds via PDF clip-path operators (pdfnative v1.1). Recommended for PDF/A and visual safety. Switches the backend to buildDocumentPDFBytes.
infoItemsNoOptional key-value metadata rows rendered below the title (e.g. date, author).
watermarkNoOptional semi-transparent text watermark rendered on every page (e.g. 'DRAFT', 'CONFIDENTIAL'). Text only in this version. opacity < 1.0 is rejected under pdfA='pdfa1b' (ISO 19005-1 forbids transparency).
cellVAlignNoVertical alignment of cell content (pdfnative v1.4). Switches the backend to buildDocumentPDFBytes.
footerTextNoOptional text rendered at the bottom of every page.
outputModeNoEither 'base64' (returns the PDF inline) or 'file' (writes to a sandboxed path inside PDFNATIVE_MCP_OUTPUT_DIR).base64
outputPathNoRequired when outputMode='file'. Relative path inside the sandbox; must end with .pdf.
cellBordersNoPer-cell vector borders (pdfnative v1.4). Switches the backend to buildDocumentPDFBytes. Choose individual sides or `all`.
cellPaddingNoHorizontal cell padding in points applied to both insets (default 3). pdfnative v1.2.
minRowHeightNoMinimum row height in points (default 12). pdfnative v1.2.
repeatHeaderNoRepeat the header row on every continuation page (pdfnative v1.2). Default true.
autoFitColumnsNoWhen true, column widths auto-fit content (pdfnative v1.1). Switches the backend to buildDocumentPDFBytes; byte output differs from the default path.
viewerPreferencesNoReader presentation hints (catalog /PageLayout, /PageMode, /ViewerPreferences). PDF/A-safe; all optional.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeYes
filePathNoAbsolute sandboxed file path (when mode='file').
sizeBytesYes
Behavior5/5

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

The description goes beyond annotations by detailing backend switches ('Switches the backend to buildDocumentPDFBytes') for certain parameters, PDF/A compatibility, watermark opacity restrictions under pdfa1b, and smart-table field behaviors. This provides rich behavioral context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with a clear main purpose followed by parameter highlights. It is front-loaded but somewhat lengthy; however, every sentence adds value for a complex tool.

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

Completeness5/5

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

Given 20 parameters, nested objects, and an output schema, the description covers key aspects: purpose, feature highlights, PDF/A, watermark limitations, output modes, and backend behaviors. It is complete for the tool's complexity.

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

Parameters4/5

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

With 100% schema description coverage, the baseline is 3. The description adds value by explaining smart-table fields (e.g., 'tagged for PDF/A', 'pdfnative v1.2') and linking parameters to backend behavior, though much is already in the schema.

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?

The description clearly states the tool generates a tabular PDF report from column headers and data rows. It distinguishes itself from siblings like add_form or add_barcode by focusing on tabular data. The verb 'Generate' and resource 'tabular PDF report' are specific and unambiguous.

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?

The description indicates ideal use cases ('data exports, financial summaries, schedules'), providing clear context. However, it does not explicitly contrast with alternatives like generate_basic_pdf or mention when not to use this tool.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Nizoka/pdfnative-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server