Skip to main content
Glama
Nizoka

pdfnative-mcp

Verify PDF signatures

verify_pdf
Read-onlyIdempotent

Verifies each PAdES digital signature in a PDF by recomputing SHA-256, validating CMS messageDigest and signatureValue, and reporting per-signature integrity, signer details, and chain trust.

Instructions

Read-only verification of every PAdES Baseline / adbe.pkcs7.detached signature in a PDF. For each /Sig widget, recomputes the ByteRange SHA-256, validates the CMS messageDigest (integrity), and verifies the CMS signatureValue with the embedded signer certificate. Supports RSA-SHA256 and ECDSA-SHA256 (P-256). The response shape: { allValid, signatureCount, summary, signatures: [{ valid, integrity, signerSubject, signingTime, reason, chainTrust: 'self-signed'|'unverified'|'trusted', errors: [] }] }. Read allValid for an overall yes/no; iterate signatures[] for per-signature detail. Without trustedRootsDerBase64, chainTrust is 'self-signed' (single-cert chain) or 'unverified' (signer rooted in an external CA).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fieldsNoOptional dot-path projection applied to the structured result (e.g. ['allValid'] or ['signatures.valid']). Composes after verbosity. Unknown paths are omitted.
pdfBase64YesBase64-encoded PDF bytes to verify.
verbosityNoResponse verbosity. 'full' (default) returns the per-signature signatures[] array; 'summary' returns a token-frugal verdict { signatureCount, allValid, invalid, summary } and drops signatures[].full
trustedRootsDerBase64NoOptional list of base64-encoded X.509 root certificates (DER). When supplied, each signer certificate is validated against these roots; otherwise chainTrust is reported as self-signed or unverified.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
summaryYes
allValidYes
signaturesYes
signatureCountYes
Behavior5/5

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

Annotations (readOnlyHint=true, etc.) are augmented with rich behavioral details: the verification algorithm (recomputes ByteRange SHA-256, validates messageDigest, verifies signatureValue), supported algorithms (RSA-SHA256, ECDSA-SHA256), and response shape. 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?

The description is concise for the information conveyed (120 words). It front-loads purpose, algorithm, and response shape. Could be slightly tighter but every sentence serves a purpose.

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 the complexity of PDF signature verification, the description covers verification algorithm, supported types, response structure, and edge cases (trusted roots). It is complete even without an output schema (though one exists).

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 is 100%, and the description adds significant value: clarifies effect of trustedRootsDerBase64 on chainTrust, explains verbosity options and fields projection, and details response structure. This goes beyond the schema's descriptions.

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 specifies 'read-only verification of every PAdES Baseline / adbe.pkcs7.detached signature in a PDF', clearly stating the verb (verify) and resource (PDF signatures). It distinguishes from siblings like sign_pdf and validate_pdf by focusing on signature verification.

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 implicitly guides usage by noting constraints on chainTrust when trustedRootsDerBase64 is omitted. It does not explicitly exclude alternatives like sign_pdf, but the context of sibling tool names provides 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