Loading ToolBench
Veryfi is a service to extract data from financial documents. It is fast, accurate, and secure. Veryfi has many endpoints. The "documents" endpoint is a misnomer. It works with receipts, invoices, and purchase orders. For other document types, it's imperative to use Veryfi's other API endpoints. The following document types have endpoints with a dedicated ML model and schema: bank checks, bank statements, W2s, W8-BEN-E, W9s, business cards
The server has a single well-documented tool with clear purpose, good descriptions, and a proper input schema. Naming is action-oriented (process_document) and descriptions are detailed and helpful. However, the tool lacks output schema documentation, error handling guidance, and permission/scope declarations. The server is functional for its narrow domain but falls short of production-grade polish. Score reflects: good naming (75/100), excellent description (85/100), complete but undocumented schema (65/100).
Extract structured data from images of receipts, invoices, and purchase orders using Veryfi's OCR technology. Returns JSON with vendor name, amounts, dates, line items, taxes, and other transaction details. SUPPORTED: receipts, invoices, purchase orders. NOT SUPPORTED: bank checks, bank statements, W2s, W8-BEN-E, W9s, business cards - users must use Veryfi API directly for these.
Output schema is not documented. The tool description states it 'Returns JSON with vendor name, amounts, dates, line items, taxes, and other transaction details' but provides no formal schema specification. LLMs cannot reliably parse unstructured output or plan downstream tool calls without knowing exact field names and types.
No error handling guidance. The tool raises FileNotFoundError and ValueError for credential failures, but provides no recovery hints to the LLM (e.g., 'Check that the file exists' or 'Verify VERYFI_* environment variables are set'). Per pattern:recovery-guide, error messages must guide the agent on next steps.
No scope/permission declaration. The tool description does not state what permissions or credentials are required (read-only access to Veryfi API, valid client ID/username/API key). Per pattern:scope-declaration, tools should declare their authority requirements for least-privilege agent configuration.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | D | 59 | <=2025-11-25 | v2 |
| 2026-03-09 | F | 46 | - | v1 |
No audit logging of tool invocation. The server logs 'Processing document' at the Python logger level but does not correlate calls with user identity, timestamps, or parameters in a structured audit trail. Per pattern:audit-trail, agent tool calls must be traceable for compliance.
STDIO-only transport limits remote accessibility. This server cannot be deployed in a hosted or managed MCP environment (e.g., Claude Desktop, web-based agent platforms). STDIO is only suitable for local development and testing.