Tools reference

Complete reference of every tool the GroupDocs.Signature MCP server exposes to AI agents, with parameters, example prompts, and results. Captured from a live tools/list call against server version 26.9.0 (raw capture: tools-list.generated.json in this section’s source).

ToolWhat it does
signSigns a document with a text, QR code, barcode, or digital certificate signature
verifyVerifies signatures in a document and reports valid/invalid counts
search_digital_signaturesReturns certificate details — signer, issuer, serial, validity, timestamp
search_qr_codesFinds QR codes and returns their decoded text, page, and position
search_barcodesFinds barcodes and returns their decoded values, page, and position
search_text_signaturesFinds embedded text signatures, stamps, and labels
search_image_signaturesFinds embedded image signatures and returns them as base64 PNGs
get_document_infoReturns file type, page count, size, and per-page dimensions
get_license_statusReports the active licensing mode and, under metered licensing, consumption

The FileInput shape

Every tool takes its document through the same file object — pass either a name from your storage folder or inline content:

{ "file": { "filePath": "contract.pdf" } }
FieldTypeDescription
filePathstringFile path or name in the configured storage folder
fileContentstringBase64-encoded file content (alternative to filePath)
fileNamestringOriginal filename with extension — required with fileContent. Since 26.9.0 it also works on its own, resolved from the storage folder exactly like filePath

You rarely write this JSON yourself: the AI agent does, from your plain-language prompt. Missing files are not an error to fear — the tool responds with the list of available files so the agent can correct itself.