Schema

Schema

Our Enterprise-grade system leverages Zod, the industry-standard validation library, to provide robust, type-safe boundaries for your mission-critical databases. Zod fully implements the Standard Schema specification, guaranteeing seamless interoperability across modern frameworks and ensuring maximum reliability for all inputs. We also enforce a Dual-Schema Pattern for bulletproof validation at both the input and output boundaries.

Enterprise Validation Rules

To provide a secure and robust integration experience, we strictly enforce the following schemas at the MCP boundary:

1. Strict Error Responses: All tools are guaranteed to return a structured error response upon failure. Our resilient design ensures you will never encounter raw, unhandled exceptions, empowering self-healing autonomous workflows. The schema is: { success: false, error: string, code: string, category: string, suggestion: string, recoverable: boolean }
2. Deterministic Table Queries: Tools that query tables will return { exists: false, table: string } if the table does not exist, enabling graceful fallback handling in your LLM workflows.
3. Sandboxed File Operations: File system interactions are strictly bounded by ALLOWED_IO_ROOTS to prevent directory traversal and ensure isolated, secure execution.

Integration Guide

Please refer to the repository source for Zod schemas (src/adapters/mysql/schemas/). We highly recommend using schema.safeParse() when building custom MCP tool execution handlers or client integrations to handle validation errors gracefully without throwing exceptions.

For runtime schema introspection, see the Code Mode documentation, which allows you to programmatically discover API parameters and return types using the .schema() introspection method.