Skip to main content
Glama
Nizoka

pdfnative-mcp

Add table / report

add_table
Idempotent

Generate a tabular PDF report from column headers and data rows. Supports wrapping, repeat header, zebra striping, and PDF/A conformance for professional data exports and summaries.

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
titleYesReport title rendered at the top of the document and used as PDF metadata title.
headersYesColumn header labels. Must have the same length as each row in `rows`.
rowsYesData rows. Each row is an array of cell strings with the same length as `headers`.
infoItemsNoOptional key-value metadata rows rendered below the title (e.g. date, author).
footerTextNoOptional text rendered at the bottom of every page.
autoFitColumnsNoWhen true, column widths auto-fit content (pdfnative v1.1). Switches the backend to buildDocumentPDFBytes; byte output differs from the default path.
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.
wrapNoCell wrap policy (pdfnative v1.2). 'auto' (default) wraps only when a cell overflows; 'always' wraps every cell; 'never' uses v1.1 character truncation.
repeatHeaderNoRepeat the header row on every continuation page (pdfnative v1.2). Default true.
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.
minRowHeightNoMinimum row height in points (default 12). pdfnative v1.2.
cellPaddingNoHorizontal cell padding in points applied to both insets (default 3). pdfnative v1.2.
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.
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.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeYes
sizeBytesYes
filePathNoAbsolute sandboxed file path (when mode='file').
base64NoBase64-encoded PDF bytes (when mode='base64').
Behavior5/5

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

The description goes beyond annotations by detailing how smart-table fields engage the document backend, specific behaviors for wrap, repeatHeader, zebra, and caption, and notes backend switching for autoFitColumns and clipCells. This gives 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 opening sentence and logical grouping of smart-table fields. It is slightly verbose but efficient for the complexity.

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?

The description covers the core table generation and PDF/A options well. It does not mention outputMode or outputPath, but since the schema provides full descriptions, completeness is adequate. The presence of an output schema reduces the burden.

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 coverage, the description adds value by grouping smart-table fields and explaining pdfnative version details, PDF/A recommendations, and row-length constraint. This extra context justifies a 4, slightly above baseline.

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, specifying ideal use cases like data exports and financial summaries. This distinguishes it from sibling tools such as add_form or generate_basic_pdf.

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 provides clear usage context ('Ideal for data exports, financial summaries, schedules') but does not explicitly exclude when not to use or name alternatives. However, the sibling list provides implicit differentiation.

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