Skip to main content
Glama
Nizoka

pdfnative-mcp

Inspect PDF metadata

inspect_pdf
Read-onlyIdempotent

Inspect a PDF to retrieve version, page count, encryption state, PDF/A claim, signatures, and attachments. Perform CI-style assertions to verify properties like pdfa, signed, encrypted, placeholder, or attachments.

Instructions

Read-only inspection of an existing PDF: version, page count, encryption state, PDF/A claim, signature count, hasSignaturePlaceholder, embedded attachments[], document info / metadata. Use the check array for CI-style assertions — supported values: 'pdfa', 'signed' (true when at least one signature has signed content), 'encrypted', 'placeholder' (unsigned /Sig widget present), 'attachments' (at least one /EmbeddedFile). The checksPassed boolean is true only when ALL requested checks hold.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
checkNoOptional CI assertions. The result.checksPassed flag is true only when every requested check holds (e.g. ['pdfa','signed']).
pagesNoWhen true, include per-page metadata in the response.
fieldsNoOptional dot-path projection applied to the structured result (e.g. ['pageCount','signatureCount']). Composes after verbosity. Unknown paths are omitted.
pdfBase64YesBase64-encoded PDF bytes to inspect.
verbosityNoResponse verbosity. 'full' (default) returns every field; 'summary' returns a token-frugal scalar subset (version, pageCount, encryption, pdfA, signatureCount, hasSignaturePlaceholder, attachmentCount) — drops the attachments[], info and perPage arrays.full

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
infoNoDocument /Info dictionary entries decoded as strings.
pdfANoDetected PDF/A claim (e.g. '1B', '2B', '2U', '3B') from XMP metadata, or null when absent.
checksNo
perPageNo
versionYesPDF version (e.g. "1.7").
pageCountYes
encryptionYes
pageLabelsNoLogical page-numbering ranges from the /PageLabels number tree (ISO 32000-1 §12.4.2), or absent when the document has none. Each range gives the 0-based first page, numbering style, optional prefix and start value.
attachmentsYesEmbedded files exposed via /Names → /EmbeddedFiles (PDF/A-3, Factur-X).
checksPassedNo
signatureCountYes
hasSignaturePlaceholderYesTrue when at least one signature widget exists with empty /Contents — i.e. an unsigned placeholder awaiting `sign_pdf`.
Behavior5/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. Description adds detailed behavior: checksPassed only true when all checks hold; verbosity and fields projection behavior. No contradictions.

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?

Single concise paragraph, front-loads purpose, then explains parameters. Efficient but could benefit from bullet points for readability.

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?

Covers all necessary aspects: purpose, parameters with behavior, CI assertions, verbosity. Output schema exists, so return values need not be detailed. No gaps given complexity.

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

Parameters5/5

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

Schema coverage 100%, but description adds significant value: explains check array values and checksPassed logic, fields dot-path and omission behavior, verbosity differences. Exceeds 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?

Description states exactly what it does: read-only inspection of PDF metadata. Lists specific items: version, page count, encryption state, PDF/A, signature count, etc. Clearly distinguishes from mutation siblings like add_attachment, sign_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?

Describes use case for read-only inspection and CI-style assertions via check array. Does not explicitly state when not to use or differentiate from validate_pdf/verify_pdf, but the read-only nature is clear.

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