verify Leave feedback

verify checks signatures in a document and reports whether they are valid, with counts. Pass type as text, qrcode, barcode, digital, or all. It is the single call behind “is this signed, and is it still valid?”. Example prompt: “Verify the signatures on contract_signed.pdf”.

Tool description (as the AI agent sees it):

Verifies signatures in a document and returns the result (valid/invalid, counts) as JSON. Supports text, QR code, barcode, and digital signatures. Supports PDF, DOCX, XLSX, PPTX, and 30+ more document formats. Call this tool immediately whenever the user asks to verify a signature, check if a document is signed, or validate a signature. Do NOT pre-check whether files exist — just pass the filename the user provided. The tool resolves files from storage and returns an error with available files if a name is not found. Returns a JSON object with isValid, succeeded (count), and failed (count) fields. On failure, the response text starts with ‘Verification failed for’ followed by the underlying exception type, message, and inner-exception chain.

{
  "name": "verify",
  "arguments": {
    "file": {
      "filePath": "contract_signed.pdf"
    },
    "type": "all"
  }
}

A JSON object with the verification outcome and counts per signature type.

Read the result precisely: a valid digital signature means the document has not changed since it was signed and the certificate chain checks out. A valid text or QR result means the expected mark is present — it says nothing about tampering. The distinction matters whenever the answer feeds a compliance decision.

On failure the text starts with Verification failed for, followed by the exception type and message.

• “Verify the signatures on contract_signed.pdf.”
• “Is this document digitally signed and still valid?”
• “Check every signature type and tell me which ones pass.”

See it used end-to-end: Verify signed documents.