Why raw database access doesn't work for production agents

Giving agents direct SQL access sounds simple until you deal with real company complexity. Here's why workflows handle it better. 🔗 Watch the full webinar: https://www.youtube.com/watch?v=mIk1pDcr30I In this clip, Marcus Dubreuil from J.W. Pepper explains what happens when simple MCP tools hit messy reality. Their order lookup process seems straightforward: query a database for an order number. But they have orders spread across three different systems: e-commerce, warehouse, and ERP. Each uses different order number formats. You could document all of this in system prompts and hope the agent figures it out, but it wouldn't be deterministic. Instead, they built a workflow that handles any order number format, runs protected SQL queries across all three systems, and returns consolidated results. The workflow acts like a microservice: small, focused, and reliable. This is what Marcus means by adding "drops of determinism" into agent capabilities. Instead of building monolithic workflows, they're creating focused tools that handle specific complexity while letting the agent manage conversation and intent. Each workflow is smaller and more maintainable than traditional iPaaS solutions. If your company has technical debt, multiple systems of record, or complex business logic that agents need to navigate, this shows why workflow tools work better than raw MCP access. #WorkflowTools #TrayAI #MCPServer #SQLSecurity #AgentBuilder #EnterpriseComplexity #Microservices #DeterministicAI #TechnicalDebt #DatabaseIntegration --------------------------------- Learn more about Tray: https://tray.ai/ Follow Tray on Twitter: https://x.com/tray Follow Tray on LinkedIn: https://www.linkedin.com/company/tray-ai/