You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[BUG] Inconsistent response format — validate_pipeline and catch-all missing success field #190
Any unhandled exception produces a response missing the success field entirely.
Impact
MCP clients (including LLM agents) that check result.get("success") will get None for both cases, making it impossible to distinguish between "tool ran but failed" vs "tool ran successfully with this result."
Suggested fix
Map valid → success in the validate_pipeline handler
Add "success": false to the server catch-all error response
Both are one-line fixes.
Found while auditing API consistency across all 34 tool functions.
Activity
SarthakB11 commentedon Apr 13, 2026
Happy to open a PR for this — have a fix ready locally.