ce5a6378 by Ean Schuessler

Fix MCP JSON Schema validation for tools/list endpoint

- Fix inputSchema properties to use quoted string keys for proper JSON Schema format
- Remove debug logging added for Accept header troubleshooting
- Remove unnecessary tools/list workaround in mcp#ToolsCall service
- The properties field in inputSchema must be a record/object, not an array
- All 6 tool schemas now properly defined with string keys: "path", "action", "renderMode", "parameters", "query", "name", "arguments"
1 parent d8ffaac1
...@@ -544,7 +544,7 @@ class EnhancedMcpServlet extends HttpServlet { ...@@ -544,7 +544,7 @@ class EnhancedMcpServlet extends HttpServlet {
544 544
545 // Validate Accept header per MCP 2025-11-25 spec requirement #2 545 // Validate Accept header per MCP 2025-11-25 spec requirement #2
546 // Client MUST include Accept header with at least one of: application/json or text/event-stream 546 // Client MUST include Accept header with at least one of: application/json or text/event-stream
547 if (!acceptHeader || !acceptHeader.contains("application/json") && !acceptHeader.contains("text/event-stream")) { 547 if (!acceptHeader || !(acceptHeader.contains("application/json") || acceptHeader.contains("text/event-stream"))) {
548 response.setStatus(HttpServletResponse.SC_BAD_REQUEST) 548 response.setStatus(HttpServletResponse.SC_BAD_REQUEST)
549 response.setContentType("application/json") 549 response.setContentType("application/json")
550 response.writer.write(JsonOutput.toJson([ 550 response.writer.write(JsonOutput.toJson([
......