No user-submitted related servers found.
Scored across 4 tools
Each tool targets a distinct verb on the PDF: inspect (read fields), fill (write new file), verify (render+OCR compare), and hash (record output). Boundaries are crisp, with no overlap, and the descriptions explicitly note scope limits (verify proves legibility, not correctness).
Consistent snake_case and a shared pdf_ prefix throughout. Minor deviation: pdf_sha256 breaks the pdf_form_* pattern and is a generic utility rather than a form operation, but it remains predictable and readable.
Four tools is lean but each earns its place in a tight fill-and-proof workflow with no redundancy. Slightly on the thin side for the implied scope, but well-scoped rather than padded.
Covers the full loop: enumerate fields, fill safely to a new file, verify rendering, and record the output digest. Minor gaps like batch/multi-file handling or field validation reporting are absent but workable given the narrow purpose.